Onbase: A Secure, Protected Environment: Critical Information Secure at Every Data State
Onbase: A Secure, Protected Environment: Critical Information Secure at Every Data State
OnBase: a Secure,
Protected Environment
Critical information secure at every data state
Security functionality is standard, OnBase is designed to be one of the most secure enterprise information platforms
whether deployed on-premises on the market. Our dedication to security gives our customers peace of mind in
the confidentiality, integrity and availability of their data.
or in the cloud
OnBase is developed with security in mind—from inception through release and
Administrators can easily beyond. Hyland employs a dedicated application security team that is tasked with
configure enhanced security carrying out advanced security practices on the software as well as training and
measures consulting company-wide on security-related matters.
1 2 3
INFORMATION IS NATIVELY SECURED AND CAN BE ENCRYPTED:
Authorized
Encrypted Encrypted User
Traffic Traffic
Web Application
Server Server
File Server Database
Unauthorized
User
No one can access private data outside
of OnBase.
Even if data is intercepted in transit, Only authorized users can access
Even if the network is broken into, there encryption ensures that the information information, as configured by the
are additional levels of protection. can’t be used. administrator.
HOW DOES THIS WORK?
1 2 3
AT REST IN TRANSIT IN USE
All data stored in the Transport Layer Security, Configurable session
system can be encrypted or TLS, is supported to timeouts prevent
with AES-256 or AES-128 protect communication unauthorized users from
(Advanced Encryption of data. OnBase always accessing any data on a
Standard, or AES). supports the latest user’s screen after a
version of TLS. specific amount of
Keyword values, used to classify time has passed (without signing
specific documents in the database, OnBase Distributed Disk Services, in using valid credentials and re-
can also be encrypted with AES-256 or DDS, uses an AES-128 encrypted authenticating OnBase).
or AES-128. Should the database be connection to ensure that if traffic is
accessed by an unauthorized user, the intercepted, data will be unreadable Keyword values may be masked,
keywords will be unreadable. and unusable. preventing unauthorized users from
viewing sensitive data.
Data exported to removable media, like
a CD or DVD, can also be encrypted.
Throughout the development process, built-in ‘gates’ require the security team to
sign off on development before the next phase can begin. The last gate is directly
SUPPORT DESIGN
before launch.
Threat modeling and risk assessments are performed throughout the entire process,
allowing the team to proactively identify and address any potential issues.
To continuously test for vulnerabilities, exploits, vectors and bugs, the team uses
various methods including:
• Secure development practices
• Automated security scanning
• Manual penetration testing
Built-In Security
Security functionality comes standard with OnBase, whether it is deployed
on-premises or in the cloud. These access controls include strict policies with
configurable complexity requirements; granular rights management that enables
admins to control access to every part of the system, to ensure that users can
only access data they are authorized to see; and security keywords that ensure
unauthorized users cannot see any data associated with a keyword they don’t
have clearance to access.
Enhanced Measures
Administrators can easily configure enhanced security measures in their OnBase
deployments. They can use encrypted disk groups and encrypted alphanumeric
keywords, both using AES-256 or AES-128 encryption. Distributed disk services can
also be used to protect data from being read if intercepted, using AES-128 encryption.
Digital signatures can be used to alert users to unauthorized content modification
after a document has been signed.
Seamless Integrations
OnBase integrates with other external security systems to create a seamless
experience for your users. Single sign-on (SSO) integrations include Active
Directory (AD), Active Directory Federation Services (ADFS), Security Assertion
Markup Language (SAML) and Lightweight Directory Access Protocol (LDAP).
Permissions in AD and LDAP solutions can also be replicated in OnBase.