KOMpliance & OnBase FAQs
We have OnBase DDS, why do we need KOMpliance?
The OnBase Distributed Disk Service (DDS) eliminates the use of network shares to access the contents of the OnBase Diskgroups through secure network access.
However, DDS cannot prevent local privileged user access to the sensitive documents stored in OnBase, and in turn cannot prevent any of these documents from being deleted, overwritten or destroyed. DDS does not address security threats that can result from users and administrators with local access or even domain admin / backup access across the network. Using DDS alone, the OnBase documents are still vulnerable to local access on the server and to any malware that is executed in the context of any power user or administrator’s privilege level, or greater. While the use of Active Directory and ACLs helps boost security, they are still not enough to ensure complete access restriction.
KOMpliance works with OnBase DDS as a fully supported integration to address these vulnerabilities. Used together, they can minimize access to protected OnBase documents, both locally and across the network, by eliminating network shares and enforce privacy by eliminating browse access, providing OnBase administrators unprecedented control for safeguarding and enforcing privacy.
Using both DDS and KOMpliance together eliminates the use of network shares to access Diskgroups and prevents all other types of access to the OnBase documents outside the context of OnBase itself. No one can browse the contents of a Diskgroup (even system administrators with full permissions), or manipulate a file managed by OnBase, or even walk the directory.
This level of protection extends to preventing file manipulation by viruses or malware.