How to Create a Customized Compliance Standard Repository Rule For the Database Target
(Doc ID 1900268.1)
Last updated on NOVEMBER 24, 2019
Enterprise Manager for Oracle Database - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 12.1] Information in this document applies to any platform.
The goal of this article is to create a custom compliance standard repository rule for a database target.
Compliance rules are a set of rules that check for adherence to Oracle best practice recommendations. A target that adheres to the best practice guidelines is considered 'compliant'. A target that does not follow the best practices is considered 'non compliant' because the compliance standard rule has been violated. Oracle provides a set of compliance standards and rules which can be associated to a to a target. For example, Cloud Control ships with the following Oracle provided database compliance standards, "Basic Security Configuration for Oracle Database", "High Security Configuration for Oracle Database","Certification for Oracle Database", "Configuration Best Practices for Oracle Database", "Storage Best Practices for Oracle Database", "Patchable Configuration for Oracle Database", "Support Policy for Oracle Database". Each of these compliance standards has a set of rules associated with it. For example the 'Storage Best Practices for Oracle Databases' consists of rules such as 'Tablespace Not Using Automatic Segment-Space Management','Insufficient Number of Redo Logs',''Checks for rollback segments in SYSTEM tablespace'
However it may be possible that extra rules are required (on top of those provided by Oracle) to ensure compliance to different local standards. This article demonstrates how a custom compliance standard can be created. This note will use the example of creating a compliance rule which checks for any users who are using the default profile.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!