Moving away from your Legacy ECM

Moving away from your Legacy ECM

Organizations can’t afford to treat security or compliance as an afterthought.

Between cyber-attacks costing companies billions of dollars, GDPR fines of up to 4% of global revenue, and new aggressive data regulations coming every day – both companies and government agencies are getting serious about how they store their data and documents.

Organizations also can’t afford to use Enterprise Content Management (ECM) systems that treat security and compliance as an afterthought.  

It’s no surprise then that organizations everywhere are looking to ditch their legacy ECMs, with the goal of finding a modern, secure, and compliant alternative.

The Tried and True Alternative

Feith is an Enterprise Content Management system that got its start selling to the DoD and US Intelligence Community. 

Since then, it’s obtained broad appeal across the Fortune 500, Universities and Civilian Government.  Why?  The answer is simple – it’s the only ECM that took Compliance and Security seriously from the start.

While other companies are scrambling to bolt Records Management features onto their software (and paying Gartner to call them leaders for it), Feith was built for secure Records Management from the start. 

In fact, Feith was the very first company to achieve perpetual certification on the Department of Defense’s Records Management standard back in 2007.  Since then, Feith has been the major thought-leader in complaint and secure Electronic Content Management.

What does all this mean to you?

It means the most advanced Records Management-enabled system on the market. A system that was designed to scale – comfortable working with hundreds of thousands of users. 

It means a system that builds Role Based Access Controls (RBAC) and Attribute Based Access Controls (ABAC) down into the foundations of the platform.  Software that has been penetration tested by the nation’s best, over and over again. 

Automatic document classifications, redactions, and PII-detection. Fully integrated workflow.  Modern APIs. And it means that, unlike most of our competitors, we’ve never given our source code to foreign governments, and never will. 


So you’re an “acquired” Documentum customer?

So you’re an “acquired” Documentum customer?

Documentum started in 1990, and quickly proved that it was a forward-looking company, a title it held for nearly two decades.  Several of the strategies Documentum developed helped to define the Document Management industry we have today.

Unfortunately, through several aggressive venture capital rounds, an IPO, and multiple acquisitions, the core of Documentum has eroded.  This proved truer than ever, when Documentum was scooped up by acquisition-hungry OpenText.

When your document management system is acquired by a publicly traded company, you are viewed as an opportunity for revenue growth.  OpenText needs to draw as much value as possible to justify their purchase to shareholders, which typically leads to:

  • dramatically rising prices;
  • reduced upgrade options;
  • promises of investment in the product which don’t materialize;
  • pressure to shift to a competing OpenText product;
  • employee churn of both product leaders and experienced programmers;
  • account management staff who are not familiar with your needs;
  • lack of long-term products vision; and
  • a loss of existing relationships with the vendor.

We would not like to be treated that way, and neither do you; so we’d like to give you an alternative.

In 1979, Don Feith started Feith Systems, a privately-held company.  We believe in personally knowing our customers, continued investment in advancing our products, and executive support for each one of our clients.  Feith’s customers are our cherished community, many of whom have been with Feith for 15+ years.

Talk to Feith if you never want to be an “acquired” customer again.

6 Mistakes You’re Making By Using Public Fileshares

If you’re using services like Google Drive, DropBox, Box.net, or SkyDrive for business, here’s why you probably shouldn’t be.

1. Trusting The Public Cloud.

Your coworkers already use applications like Google Drive and Dropbox to share business documents because they are easy to use, but security can be questionable. You should limit users from taking corporate files to the Public Cloud before important information is compromised.

2. Ignoring Your Snowden or Manning While He’s Right Under Your Nose.

Identifying a thief after they’ve gotten away isn’t helpful. Stopping them in the act is. When a file sync and share can report suspicious activity as it happens by monitoring who’s accessing what and how many files, you stop the offender before confidential or damaging documents walk out the door.

3. Disregarding Proper Records Management.

Documents in the Public Cloud are not managed through your Records Management application, are not categorized, administered, or disposed of automatically, and are not conformant to DoD 5015.2. Only when you sync documents with databases that are RMA’d can you start proper records management.


4. Running on Non-Standard Databases.

Oracle Database? SQL Server? Your organization’s technology and staff grow around a specific database. Therefore it’s critical to use, create, and maintain business applications like an enterprise file sync and share that run on that existing database.

5. Forgetting That Your Users Are Already The Users.

Every new application added to a user management platform should tie authentication to the central system, such as Active Directory. It’s unwise to implement a rogue program like a Public Cloud file sync and share that ignores the security and consistency of that process.

6. Losing Your Stuff.

As large numbers of documents are added to the cloud, the only way to easily find the one you’re looking for is through the document’s content. Only an enterprise file sync and share that accesses a universal full-text searchable repository (including OCR’d image content), and uses a familiar interface with which to search it, can do that.