Configuration Monitoring and Logging - Security Best Practices - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Security Best Practices

Security Best Practices
Foundation 23.1

The current configuration of your OnBase environment should be charted and any changes to that configuration should be documented. This enables you to track what should be happening in your environment, based on its configuration, and allows you to identify discrepancies that could indicate unauthorized access or use. It also allows you to establish performance benchmarks that can expose performance degradation issues.

The scope of your monitoring must also allow for the complexity of the configuration of your system. For example, it may not be possible to track the addition or modification of every Document Type, Keyword Type, or even user account, but you can track which users and User Groups have the administrative permissions required to make those kind of changes. This level of charting can help focus your review on the types of changes being made, rather than the specific changes, to help establish patterns of acceptable modifications to the system.

OnBase also provides robust logging capabilities for all areas of the solution. In addition, third-party software used in OnBase environments, such as Microsoft IIS, should be leveraged for their logging capabilities. It is a best practice to synchronize the clocks on the various servers in a solution, making it easier to correlate activity in logs from different sources. Log correlation software can also be used to help organizations analyze multiple logs in a single, organized view.