Securing your Oracle Enterprise Manager deployment involves securing all layers of the stack starting with the underlying operating system (OS) on which the OMS and Repository reside all the way up to the Enterprise Manager components themselves. These recommendations will increase overall security as well as prevent certain DoS attacks.
Harden the machines themselves by removing all unsecure services such as rsh, rlogin, telnet, and rexec on Linux platform (for the list of unsecure services and how to remove them on different platforms, please refer to the CIS benchmarks). It is also recommended to stop non-essential services, this minimizes the ’attack footprint' of the host and reduces resource consumption by services that are not required, freeing up system resources to deliver the best performance from the OMS.
Restrict OS access by supporting only indirect or impersonation-based access to all Oracle Homes by using utilities such as sudo or PowerBroker. Protect the WebLogic Server Home directory, especially the domain directory which contains configuration files, security files, log files and other Java EE resources for the WebLogic domain. Grant only one OS user who runs WebLogic Server the access privilege to the directory.
Ensure that all the Oracle Homes are patched with the latest CPU (Critical Patch Update). This is a recommended best practice for securing the Oracle Management Service, Repository, Agents and managed targets. Setup your My Oracle Support credentials to detect new Security Alerts and CPUs from the Patch Advisor. With the default Security Recommendations for Oracle Products compliance standard, when a target is missing the latest Security patches, a compliance standard violation will be triggered. In addition, the Secure Configuration for Host should be associated to the hosts of the OMS and Repository. There are additional compliance standards for Database and WLS that can be applied depending on your level of security. Review the Oracle Enterprise Manager Cloud Control Administrator's Guide section on Compliance for more information on available compliance standards and how to associate targets.
The OMS runs on top of the Oracle WebLogic Server. Most of the best practices for securing Oracle WebLogic Server are applicable for securing the OMS as well. Refer to the Oracle Fusion Middleware Securing a Production Environment for Oracle WebLogic Server section Securing Oracle WebLogic Server for additional information.
Ensure that the OMS, Repository and Agent are monitored for filesystem space. The OMS writes a lot of information to log and trace files, and proper space needs to be available for successful operation and troubleshooting. The Agent also relies on filesystem space for log and trace files as well as collecting target metrics.
Remove unsecure services and stop non-essential services on all infrastructure components
Restrict OS access and protect critical files and directories
Apply latest OS security patches
Adhere to security Compliance Standards and apply latest Oracle CPU patches to all components (OMS, Repository and Agent)
Monitor filesystem space for OMS, Repository and Agent
In addition to the above recommendations, steps are necessary to secure the Oracle Management Repository. Since the Oracle Management Repository resides within an Oracle database, a number of the best practices for securing the Oracle database itself are applicable to securing the Repository as well. For best practices on Oracle database security, please refer to the Oracle Database Security Checklist.
The above document also covers certain Operating System level steps that need to be performed to secure the database. Following are additional recommendations to be implemented in the Enterprise Manager deployment.
Enable Advanced Security Option (ASO) between the OMS and Repository to ensure that the data between the OMS and Repository is secure both from confidentiality and integrity standpoints. In addition to the ASO configuration required on the Repository database, you will need to configure the OMS and Agent to connect to a secure Repository database. The detailed instructions for implementing ASO for Enterprise Manager can be found in the Enterprise Manager Security section of the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Please refer to the Oracle Database Advanced Security Administrator's Guide to obtain detailed information about ASO.
Restrict network access to the host on which the Repository resides by putting the repository database behind a firewall and checking network IP addresses. The Listener should be configured to accept requests only from OMS nodes by adding the following parameters into TNS_ADMIN/protocol.ora file:
tcp.excluded_nodes = (list of IP addresses)
tcp.invited_nodes = (list of IP addresses), list all OMS nodes here)
The first parameter turns on the feature whereas the latter parameters respectively deny and allow specific client IP addresses from making connections to the Oracle listener. Please refer to the Secure the Network Connection section of the Oracle Database Security Guide for more information.
Audit all SYS (schema) operations at the database level by setting AUDIT_SYS_OPERATIONS = TRUE.
Use the operating system syslog audit trail to minimize the risk that a privileged user, such as a database administrator, can modify or delete audit records stored in an operation system trail if the database version of Repository is 10gR2 or after.
For 10gR2 DB, refer to the Auditing documentation to obtain more information about syslog audit trail.
For 11g DB, set AUDIT_SYS_LEVEL initialization parameter appropriately to use syslog audit trail. Refer to the 11g documentation for details.
Users should log in to the Console with their own individual accounts, and not use the SYSMAN user. SYSMAN is the schema owner and is more privileged than Enterprise Manager Super Administrators. Multiple users should be granted Super Administrator to reduce the need for SYSMAN access. One strong reason for creating multiple Super Administrator accounts is to ensure one user maintains account access in case another user becomes locked out by a dictionary/brute force attack. The Super Administrator privilege should be limited to users who truly need all the permissions that Super Administrator gives them.
In some cases, you may wish to prevent SYSMAN from logging into the console by executing the following SQL statement on the Repository database as the SYSMAN user:
UPDATE MGMT_CREATED_USERS SET SYSTEM_USER='-1' WHERE user_name='SYSMAN'
After disabling SYSMAN from logging into console, you can enable it by executing:
UPDATE MGMT_CREATED_USERS SET SYSTEM_USER='1' WHERE user_name='SYSMAN'
Use password profiles to enforce the password control of Enterprise Manager Administrators while Repository-based authentication is used. There is an out-of-box password profile MGMT_ADMIN_USER_PROFILE with the following parameter settings for Enterprise Manager Administrators:
The out-of-box password verification function MGMT_PASS_VERIFY will ensure that the password cannot be same as username, its minimum length is 8, and it must have at least one alphabet, digit and punctuation character. You can create customized password profiles with different values to meet your special requirements, for example, a new password verification function to meet a stricter password complexity requirement.
Change SYSMAN and MGMT_VIEW users' password on a regular basis using only the method documented in the Security section of the Oracle Enterprise Manager Cloud Control Administrator's Guide. The documented command (update_db_password()) helps you change the SYSMAN related passwords in the OMS and in the repository database. If you do not execute this command properly, the OMS may fail to start due to inconsistent passwords for one of the many accounts. You will be prompted for the old and new SYSMAN passwords.
When changing the MGMT_VIEW password, you can select ”-auto_generate” to generate a random password that no one will know. The MGMT_VIEW password is used only by the Reporting system and should not be used for login, therefore the auto_generate flag can ensure the password is not known.
To avoid the service interruption due to the lockout of internal users, SYSMAN and MGMT_VIEW users are associated with MGMT_INTERNAL_USER_PROFILE upon install. The password parameters are all set to UNLIMITED. In addition, to avoid sessions hanging or taking a long time due to resource consumption limit, MGMT_INTERNAL_USER_PROFILE's kernel parameters are set to default, which is unlimited as well.
The Encryption Key is the master key that is used to encrypt/decrypt sensitive data, such as passwords and preferred credentials, stored in the Repository. The key itself is originally stored in the Repository and removed automatically once the installation is done. It only needs to be in the Repository during an upgrade. By storing the key separately from the Enterprise Manager schema, we ensure that the sensitive data such as Preferred Credentials remain inaccessible to the schema owner and other SYSDBA users (privileged users who can perform maintenance tasks on the database). Keeping the key outside of the Enterprise Manager schema will ensure that sensitive data remain inaccessible while Repository backups are accessed. Further, the Enterprise Manager schema owner (SYSMAN) should not have access to the OMS Oracle Homes to prevent reading or overwriting the emkey. See the Oracle Enterprise Manager Cloud Control Administrator's Guide for more detailed information about Enterprise Manager's Cryptographic Support and the emkey. Follow the process outlined below to secure the encryption key.
Backup the encryption key to a file by running the following command and keep the encryption file on a separate machine securely, restrict access to only the OMS software owner. If the encryption key is lost or corrupted, the encrypted data in the repository is unusable.
$ emctl config emkey –copy_to_file_from_credstore –emkey_file emkey.ora
The encryption key is required to be in the Repository for some operations such as Enterprise Manager patches and upgrades.
Remove the key from the Repository once the operation is done.
$ emctl config emkey –remove_from_repos
Enable Advanced Security Option on the Repository database and configure OMS and Agent
Restrict network access to known targets
Grant Super Administrator privilege to select administrators and do not log in with SYSMAN account
Enable strong password profiles and change application related account passwords regularly
Secure and backup the encryption key
For better security during agent installation, agents should be deployed using Enterprise Manager Enterprise Manager's Agent Deploy which uses the secure SSH protocol. When manually deploying Agents, to protect against the possibility of users installing unauthorized agents, use one-time registration passwords that have a reasonable expiry date instead of persistent registration passwords. Registration passwords can be created in the Console or by using the emctl secure setpwd command.
Install the agent as a separate user from OMS installation and support only impersonation based access to this account such as sudo or PowerBroker post installation to prevent unauthorized changes.
Utilize the Enterprise Manager Agent Deployment method for Agent installations.
Use a one-time registration passwords with expiry dates
Install the Agent as a separate user from OMS or Targets
Note:Agents on remote servers need to be installed as a separate OS user of the targets on that server, however, this does not apply to chained Agents. A chained Agent cannot be installed as a separate user because it gets installed along with the OMS.
There are several ways to secure the communication between OMS and agent, including firewalls, the OMS secure-lock feature, enabling TLSv1, enabling strong cipher suites and certificates. The following section looks at these in more detail.
Enterprise Manager uses the industry-standard Internet Control Message Protocol (ICMP) echo request to check status of target host machines if the agent has not uploaded or responded in a timely fashion or at expected intervals. If ICMP is disabled, the target will appear to be down. Firewall should be configured to allow ICMP to prevent false down target alerts.
A Beacon is a target that allows the Management Agent to remotely monitor services. A Beacon can monitor one or more services at any point in time. ICMP and User Datagram Protocol (UDP) are also used to transfer data between Beacon targets that allow an Agent to monitor services and the network components you are monitoring. If there is a firewall or ACL between the Web application components and the Beacons you use to monitor those components, you must configure it to allow ICMP, UDP, and HTTP traffic.
When the host where the agent resides is protected by a firewall, you need to configure the agent to use a proxy, or configure the firewall to allow incoming communication from the OMS. To configure the firewall you must determine the port assigned to the agent and whether communication is HTTP or HTPS. You can find this information by running emctl status agent.
To configure the proxy set the following properties using the Enterprise Manager Console to edit the Agent properties or emctl setproperty agent and restart the agent. The proxy realm, user and password may not be required in all environments.
$ emctl setproperty agent -name REPOSITORY_PROXYHOST -value proxy42.acme.com $ emctl setproperty agent -name REPOSITORY_PROXYPORT -value 80 $ emctl setproperty agent -name REPOSITORY_PROXYREALM –value <value if needed> $ emctl setproperty agent -name REPOSITORY_PROXYUSER –value <value if needed> $ emctl setproperty agent -name REPOSITORY_PROXYPWD –value <value if needed>
In cases where the Oracle Management Service is behind a firewall, configurations will be needed to allow proxy communications to the agents or incoming communication through the firewall.
If the agents that are behind the firewall are in different domains, you can configure the proxy to allow communication for those agents and use the dontProxyFor parameter to identify the agents within the firewall. To configure the proxy on the Management Service set the following properties using emctl set property. The proxy realm, user and password may not be required in all environments.
$ emctl set property -name REPOSITORY_PROXYHOST -value proxy42.acme.com $ emctl set property -name proxyPort -value 80 $ emctl set property -name dontProxyFor –value ”.acme.com, .acme.us.com”
To configure the firewall to allow inbound communication from the agents for metric uploads, the firewall must be configured to accept HTTP/HTTPS traffic on the upload ports. The default ports are 4889 (HTTP) and 1159 (HTTPS). If your ports were customized you'll need to use those ports.
If there is a firewall between your browser and the Enterprise Manager Console, you must configure firewall to allow the console to receive HTTP/HTTPS traffic over port 7788/7799 (defaults). You can validate your port by looking at the URL you access the Console with.
Additional component installations such as JVMD, APD and BI have additional port requirements. For example, if BI Publisher is installed additional ports may be needed for access to the reporting console. Default ports are 9702/9703 (http/https). For more information please see the documentation specific to the component.
To manage the database targets that are configured behind firewalls, you must allow Oracle Net traffic on the listener ports (typically 1521 but often customized). For more information regarding configuring Oracle Databases for firewalls see the Oracle Database 2 Day + Security Guide.
SHA (Secure Hash Algorithm) is a federal standard for secure hashing algorithms that make digital authentication and integrity validation possible. SHA1, which was originally published in 1995, has security vulnerabilities and has since been superceded by the cryptographically stronger SHA2 standard. SSL certificates using the SHA1 hash function should be switched over to the newer SHA2 hash function to maintain the highest level of secure communication.
For any SSL connection, SHA2 is used in two places:
Certificate Signature: Validates the integrity of the certificate.
The Certificate Signature is the encrypted hash of certificate. The hashing algorithm used here will be selected when issuer signs the server certificate.
MAC (Message Authentication Code): After the initial SSL handshake, a client and server communicate in encrypted mode. A MAC provides a means of integrity checking for the encrypted data. The hash algorithm used by the MAC will be decided based on the cipher suit selected during the handshake. For example: SSL_RSA_WITH_RC4_128_SHA. In this example, SHA would be used for the MAC.
Per Oracle Software Security Assurance Standards, SHA1 is allowed with TLS/SSL. SHA2 is supported in TLS/SSL MAC from TLS 1.2 only.
The following table lists the level of SHA2 support for different versions of Enterprise Manager.
|Enterprise Manager Version||SHA2 Certificate Support||Is the default Agent and OMS Certificate SHA2?||SHA2 in the MAC/Cipher Suite (TLS 1.2 support)|
* For Enterprise Manager 13c Release 1, TLS 1.2 communication is not supported between the Management Agent/Oracle Management Service (OMS) and a database target.
You can determine what certificates are being used within an Enterprise Manager environment via the Security Console. The console displays information about your current certificate configurations, thus allowing you to determine whether or not you need to update certificates to SHA2.
To access the Security Console in Enterprise Manager Cloud Control:
From the Setup menu, select Security, and then Security Console. The Security Console displays:
Click Secure Communication in the right pane, then click on the Current Configuration tab.
To check the Oracle Management Service (OMS) upload certificate:
From the Security Console, navigate to the OMS Secure Configuration region and click the Details link located in the in the Certificate Details column to display the Console Certificate Details dialog.
If the Algorithm value is SHA2, you can ignore the remaining steps of this section. If not, continue to step 3.
Check if the Issuer column value is set to the OMS default certificate authority (CA), such as EnterpriseManager on omshostname.
If Issuer is not set to the OMS default CA, you are using a third-party CA certificate. If this is the case, you can skip step 4 and go to step 5.
If the OMS default CA is used:
Check whether the OMS CA certificate is SHA2 or not. In the Certificate Authority Details region, check the Algorithm column.
If the OMS CA certificate is SHA2, use the
emctl secure oms command to update the OMS certificate (SLB certificate in the case of BIGIP). This will issue a new SHA2 certificate. You will not need to re-secure the Agents.
If the OMS CA certificate is not SHA2, then do following:
A. Create a new CA using the
emctl secure createca command. This will not change the OMS certificate. See the following for details on using this command:
B. Secure all Management Agents using the
emcli secure_agents command to secure multiple Agents in bulk. See the following for details on using this command:
This can be done is phases. Agents using the old certificate and trust store will still work until the OMS is re-secured.
C. Once all Management Agents are secured (you can check the status in Agent Certificate Details region), use the
emctl secure oms command to update the OMS certificate with the new CA. See the following for details on using this command:
Because the Management Agents were secured with the new CA details, they will continue to work without further changes.
If a third party CA certificate is used:
Get a new SHA2 certificate with the same CA, use the
emctl secure oms command to update it. You don't have to re-secure the Management Agents.
If the new SHA2 certificate has a different CA:
A. Update the Enterprise Manager trust store using the
emctl secure oms -trust_certs_loc <loc> command. The new trust store should have both the old CA and new CA certificates.B. Because the OMS is still using the old certificate, the Management Agents will work. Re-secure all Management Agents in the environment using the
emcli secure_agents command.
C. Secure all OMS instances using the
emctl secure oms command to update them with the new certificate.D. Although not mandatory, it is good practice to remove the old CA from the trusted store, then re-secure all Management Agents to update the trust store on the Agent side.
Note:If you are running Enterprise Manager is a high availability configuration with a load balancer, refer to the high availability chapters in the Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide for information on securing the OMS.
To secure Management Agents in bulk, use the
emcli secure_agents verb.
Navigate to the OMS Secure Configuration region of the Security Console and click Details in the Certificate Details column for the console port.
The Console Certificate Details dialog displays. Ensure that the Algorithm value is not SHA1 or MD5. It can be SHA2 (SHA256, SHA512. etc.).
If the Algorithm value is not SHA2, use the
emctl secure oms command to update the OMS instance.
The OMS CA certificate is used to issue a certificate for the OMS and its associated Management Agents by default. Ensure that the OMS CA certificate is SHA2 as it will issue identical certificates.
Navigate to the Certificate Authority Details region of the Security Console and ensure that the value in the Algorithm column is SHA2.
If the Algorithm value is not SHA2, then use the
emctl secure createca command to create new CA with the SHA2 algorithm.
After the new CA is created, all certificates will be issued by this new CA. For this reason, you should first secure all Management Agents before securing the OMS.
Review the certificates for all Management Agents in the Agent Certificate Details region of the Security Console.
If the certificate for a Management Agent is not SHA2, you need to re-secure the Management Agent. Before you re-secure the Management Agent however, ensure that the OMS CA is SHA2.
To secure Management Agents in bulk, use the
emcli secure_agents verb.
If you are using custom certificates on the Management Agent side as well, see the following My Oracle Support note:
12c Cloud Control: Steps to Import Third Party Trusted SSL Certificate into 12c Cloud Control Agent URL (Doc ID 1593183.1)
You can also use the following database queries to identify SHA1 or MD5 certificates:
List Agents using SHA1 or MD5 certificates
select * from mgmt_agent_sec_info where sign_alg in ('md5', 'sha1');
List CAs using SHA1 or MD5 certificates
select * from mgmt_sec_info where sign_alg in ('md5', 'sha1');
List OMS upload ports using SHA1 or MD5 certificates
select * from MGMT_OMS_UPLOAD_SEC_INFO where sign_alg in ('md5', 'sha1');
List OMS console ports using SHA1 or MD5 certificates
select * from MGMT_OMS_CONSOLE_SEC_INFO where sign_alg in ('md5', 'sha1');
The Security Console is available to Super Administrators only and provides all security related configuration information in one location, allowing you to view, analyze, and optimize security for your managed environment. To access the Security Console, from the Setup menu, select Security, and then Security Console.
When the Security Console first displays, it is divided into two main windows, the menu window on the left hand side and the information window on the right hand side.
The Security Console contains both static (text) and dynamic information. The text is to provide quick, high level context to the data, it is not intended as a replacement to your documentation.
The Security Console is categorized into the following security areas:
The overview section gives a high level description of each of the Security Console categories.
The Pluggable Authentication section is further divided into two tabs. An "Overview" tab and a "Configuration" tab.
The Overview section contains text from the documentation, however, it is not meant as a replacement for the documentation. Enterprise Manager Authentication is the process of determining the validity of the user attempting to access Enterprise Manager. The authentication feature is available across the different interfaces such as the Enterprise Manager console and the Enterprise Manager Command Line Interface (EM CLI). Oracle Enterprise Manager 12c relies on the WebLogic Server for external Authentication methods. For this reason, Enterprise Manager 12c can be authenticated using any authentication method supported by Oracle WebLogic Server.
This section displays the current configuration information in your enterprise relating to Authentication.
Authentication Mode: This parameter provides information on the various pluggable authentication schemes configured in your Enterprise Manager environment.
External User Support Enabled: Displays if you have external user authentication enabled. If using any authentication other than "repository" authentication, this will display "yes".
Auto-provisioning supported: The status of auto-provisioning is also displayed. Auto-provisioning allows for an externally authenticated user to log into Enterprise Manager without being preconfigured within Enterprise Manager and the information is transferred from the authentication application. It requires that the OMS property oracle.sysman.core.security.auth.autoprovisioning be set. For more information please see Chapter 2, "Security Features," Section 2.1.8, "External Authorization using External Roles."
When creating an Administrator (Setup->Security->Administrators menu) you enter the type of password profile you want that user to use during login. This table gives a count of the number of users in Enterprise Manager which have been assigned the various password profiles. For more information on password profiles see Section 126.96.36.199.3, "Securing User Accounts."
Enterprise Manager implements granular privileges to control access to targets, and other resources, allowing administrators to better segregate their duties. For example, consider the provisioning designer and provisioning operator job responsibilities. The former has greater responsibilities (creates components in the Software Library) than the latter (submits deployments). Flexible DB Access Control explains the privileges and roles and how they serve to provide various levels of access control to different applications, groups, services and targets within Enterprise Manager. Information about the Administrators last login to the system, their number of privileges and roles granted and recommendations on best practices relating to appropriate usage of roles and privileges can be found in this section.
The Flexible DB Access Control area is divided into five tabs, An Overview, Administrators tab, Privileges tab, Roles tab and Privilege Propagation Aggregates tab.
Giving the same level of access to all systems to all administrators is dangerous, but individually granting access to tens, hundreds, or even thousands of targets to every new member of the group is time consuming. With Enterprise Manager's administrator privileges and roles feature, this task can be performed within seconds, instead of hours. Authorization controls the access to the secure resources managed by Enterprise Manager via system, target, and object level privileges and roles.
This section describes Enterprise Manager's Authorization model including user classes, roles, and privileges assigned to each user class. The following topics are described:
Classes of Users
Privileges and Roles
Oracle Enterprise Manager supports different classes of Oracle users, depending upon the environment you are managing and the context in which you are using Oracle Enterprise Manager. There are three administrator access categories:
Super Administrator: Powerful Enterprise Manager administrator with full access privileges to all targets and administrator accounts within the Enterprise Manager environment. The Super Administrator, SYSMAN is created by default when Enterprise Manager is installed.The super administrator account can manage all other administrator accounts and set up all administrator credentials. The super administrator can:
Create Enterprise Manager privileges and roles
Perform the initial setup of Enterprise Manager, for example, defining e-mail configurations and defining global notifications rules
Add targets to Enterprise Manager
Perform any action on any target in the system
Administrator Regular Enterprise Manager administrator.
Repository Owner Database administrator for the Management Repository. This account cannot be modified, duplicated, or deleted.
Privileges and Roles
User privileges provide a basic level of security in Enterprise Manager. Privileges can be divided into two categories: Target Privileges and Resource Privileges
A role is a collection of Enterprise Manager resource privileges, or target privileges, or both, which you can grant to administrators or to other roles. These roles can be based upon geographic location (for example, a role for Canadian administrators to manage Canadian systems), line of business (for example, a role for administrators of the human resource systems or the sales systems), or any other model.
Enterprise Manager Cloud Control 12c comes with predefined roles to manage a wide variety of resource and target types.
Enterprise Manager Cloud Control 12c can be integrated with external authorization source like Active Directory by defining External roles.
Secure privileges like FULL_CREDENTIAL,FULL_JOB etc which are not granted to Super Administrators by default, can be granted to a private role.
Private roles can not be converted into System Roles. Creator of a private role handles the life cycle of it.
Private roles can be granted to administrators 'WITH_ADMIN' option from Enterprise Manage command line interface (EMCLI) which will enable administrators to grantor revoke private roles to/from other administrators.
This lists all the Administrators current created in Enterprise Manager, and also lists the date and time in which they last logged in.
This lists the top five administrators with the number of privileges directly granted to them. Administrators with high numbers of privileges indicate an inefficient use of privileges and should be directed to use roles instead. It is recommended that an Administrator be granted the minimum number of privileges necessary to perform their task. For more information on privileges and roles, see Section 2.2.3, "Managing Privileges with Privilege Propagating Groups".
This section also displays all the Target and Resource Privileges available in Enterprise Manager, whether the privilege can be applied to a single target, a specific target, a target type and if that privilege contains another privilege.
This section allows us to view the top 5 Administrators with the Highest Number of Roles, if the number of role grants is high, it points to an inefficient role hierarchy, suggesting that roles could be combined for efficient manageability.
Roles with the Highest Number of Nested Roles can also be displayed here.
An aggregate target is a target that consists of one or more member targets, such as groups and systems. Enterprise Manager support two type of aggregate targets based on privilege propagation mechanism:
Normal aggregate target - If any privilege is granted on aggregate target, only view privilege will be propagated to its members
Privilege Propagating aggregate target - If any privilege is granted on aggregate target then the same privilege will be propagated to its members
The following features are supported in case of target privileges on Aggregate Targets:
Separation between the privilege grants on aggregate target and its members
Along with the default existing behavior of propagating the same privilege on members, User can choose to have one privilege grant on aggregate target and another on its members.User can also choose to have no privilege on members.
In case of non privilege propagating aggregate targets by default only view will be granted to the members where as in case of privilege propagating aggregate targets whatever privilege is specified by the administrator that will be granted appropriately.
This feature is available from User and Role management pages as well as Target Access Page in the user interface.On these pages click on "Advanced Privilege Settings" button on top of Target Privileges table to see the advanced privileges in the table.
EM CLI support is also available for this new feature.Please check EM CLI help for existing relevant verbs for more details on the usage.
Consider the following snapshot of the target privileges for a given administrator:
Privileges listed under column ”Manage Target Privilege Grants" are applicable to the Group as well as the members.
Privileges listed under column ”Manage Aggregate Only Privilege Grants" are applicable only on the Group.
Privileges listed under column ”Manage Member Only Privilege Grants" are applicable only on the members.
In the following example PPG_DB_group1 is a privilege propagating group of database targets. PPG_HOST_group2 is a privilege propagating group of host targets. NORMAL_group1 is a non-privilege propagating group.
|Name||Type||Manage Target Privilege Grants||Manage Aggregate Only Privilege Grants||Manage Member Only Privilege Grants|
Consider the first row in the above table. This configuration means that the given user has View privilege on group PPG_group1 as well as the members. Along with that it has Configure Target privilege only on the group PPG_group1 and Blackout Target privilege only on members. This means that the current user in the picture can create Blackout on the members of group PPG_group1 but cannot do so on the group itself and it can configure PPG_group1 but cannot configure the members. The user has View on group as well as the members.
Consider the second row.PPG_HOST_group2 is a privilege propagating group. This configuration means that the given user has Configure Target privilege only on the group PPG_group2 and it does not have even View on members.
In the third row one can see a non privilege propagating group where the user is having Blackout Target privilege on the group and View privilege on the members.
Note that the two new advanced privileges column values are not applicable in case of non aggregate target like host target.
Note that the above mentioned feature is applicable to all Aggregate Targets in general. The above example shows one of Aggregate Target type (Group).
This section provides a high-level overview of Secure Communication terms and protocols used within Enterprise Manager. You can also view the current status of secured Enterprise Manager components, their certificate issuers, and details.
Enterprise Manager Framework Security implements the following types of secure connections between the Enterprise Manager components:
HTTPS and Public Key Infrastructure (PKI) components, including signed digital certificates, for communications between the Management Service and the Management Agents.
Oracle Advanced Security for communications between the Management Service and the Management Repository.
To enable Enterprise Manager Framework Security for the Management Service, you use the emctl secure oms utility, performs the following actions:
Generates a Root Key within your Management Repository. The Root Key is used during distribution of Oracle Wallets containing unique digital certificates for your Management Agents.
Modifies your WebTier to enable HTTPS channel between your Management Service and Management Agent.
Enables your Management Service to accept requests from Management Agents using Enterprise Manager Framework Security.
When you install the Management Agent on a host, you must identify the Management Service that will be used by the Management Agent. To enable Enterprise Manager Framework Security for the Management Agent, use the emctl secure agent utility.
It is important that only secure Management Agent installations that use the Management Service HTTPS channel are able to upload data to your Management Repository and Cloud Control console is accessible via HTTPS only.
Enterprise Manager uses the Agent Registration password to validate that installations of Oracle Management Agents are authorized to load their data into the Oracle Management Service.
The Agent Registration password is created during installation when security is enabled for the Oracle Management Service. You can add/edit/delete registration passwords directly from the Enterprise Manager console.
Agent Certificate Details: Displays secured agents along with their certificate details, including the algorithm, its strength, when it was created, when it expires and when the agent was secured.
Number of Unsecured Agents: Indicates the number of Agents in your enterprise that are currently operating unsecured.
Number of Expired Registration Passwords: Indicates the number of Agents which have stopped running due to an expired certificate.
Certificate Authority Details: Lists the certificates being used in your Enterprise Manager installation.
OMS Secure Configuration: Details the Enterprise Manager configuration and communication with the Management Services and indicates the secure configuration details of each, including the console and upload certificate details along with the SLB details.
Following are the configuration details about encryption between the OMS and Management Repository/Target Database. The list of encryption algorithms and the checksum algorithms that the client supports are mentioned below. For more details refer to the section "Enabling Security for the Management Repository Database" above.
Encryption Algorithms Supported: lists all the encryption algorithm details supported
Encryption Algorithm In Use: Lists the current Algorithm being used
Checksum Algorithm Supported: lists the checkup Algorithm currently supported. Which are MD5, SHA1
Checksum Algorithm in use: Lists the Algorithm currently in use
Credentials like user names and passwords are typically required to access targets such as databases, application servers, and hosts. Credentials are encrypted and stored in Enterprise Manager. Beginning with Enterprise Manager 12c, the credential subsystem supports, in addition to basic username-password, strong authentication schemes such as PKI, SSH keys and Kerberos. SSH key based host authentication, used by jobs, deployment procedures and other Enterprise Manger subsystems, is now supported.
By using appropriate credentials, you can:
Collect metrics in the background as well as real-time
Perform jobs such as backup, patching, and cloning
Perform real-time target administration such as start, and stop
Connect to My Oracle Support
Based on their usage, credentials can be classified into the following categories:
Credentials Management Current Configuration
Encryption Key: The Encryption Key is the master key that is used to encrypt/decrypt sensitive data, such as passwords and preferred credentials that are stored in the Repository. The key is originally stored in the Repository and is removed from the Repository and copied to the Fusion Middleware managed Credential Store during installation of the first OMS.
Credentials Management Usage Statistics
The Usage Statistics tab provides credential usage information.
Comprehensive Auditing shows the current auditable operations and whether they have been configured for external backup to disk. Statistics on the top five most used operations are also displayed, as well as the most active Administrators.
All operations performed by Enterprise Manager administrators, such as creating users, granting privileges, starting a remote job like patching or cloning, need to be audited to ensure compliance with the contracted internal controls of a service organization.
Non-repudiation is the central tenet of auditing. Enterprise Manager Comprehensive auditing provides a tamper-free audit trial of all critical operations.
From the Usage tab, you can view:
Current Auditing Configuration
Specific Audit Operations
Audit Usage Statistics (Top 5 Operations in the last 7 days and Top 5 Administrators in the last 7 days)
Active User Session Count shows information related to the session management, such as session timeout, max and active sessions per user count.
All authenticated open user sessions can be viewed from this area.
From the Active User Session Count area, you can view:
Session Settings (Session Timeout, Maximum Number of Sessions Allowed Per User, Permitted Number of Active Sessions )
Based on observations of information in the above categories, best practices advice is indicated in this section and covers areas such as management of the repository encryption key and auditing operations management. You can quickly view Enterprise Manager security configuration adherence to recommended Oracle security protocols. In addition, suggested best practices are provided based on the specifics of your Enterprise Manager environment.
From the Best Practices Analysis area, you can view:
Pluggable Authentication: Best practice advice tailored to the pluggable authentication scheme of your environment.
Flexible DB Access Control: Best practice advice pertaining to role and privilege management.
Secure Communication: Best practices regarding secure communication between the Management Service, Agent, and Enterprise Manager console.
This section covers the following SSL Guidelines:
Oracle recommends that you configure the OMS and Agents to support only the TLS v1 protocol, which is the successor of SSL v3, for the communication. By default the OMS is configured in mixed-mode, accepting both SSLv3 and TLSv1 protocols.
To configure OMS for the TLS v1 protocol only:
Enter the following command to stop the OMS:
<OMS_ORACLE_HOME>/bin/emctl stop oms
Enter the following command:
<OMS_ORACLE_HOME>/bin/emctl secure oms -console -protocol TLSv1
Append the following to the JAVA_OPTIONS in
Domain_Home/bin/startEMServer.sh. If this property already exists, update the value to TLS1.
Enter the following command to restart the OMS:
$ emctl start oms
To configure an Agent to support only TLS v1 protocol while the Agent listens as a server, edit the Agent properties in the Enterprise Manager Console or use emctl setproperty at the command line. To edit multiple Agents at a time, go to Setup -> Agents, select the Agents you want to modify, click Properties. This will create a job and you can specify the Agent property changes on the Parameters page that will get applied to all selected Agents. To use the command line, issue the following:
$ emctl setproperty agent -name allowTLSOnly -value true
The Oracle Management Service and Oracle Management Agents can run in non-secure (HTTP) or secure (HTTPS) modes. The recommendation is to always use secure mode, hence the default installation will automatically secure-lock the OMS. The secure-lock mode takes security one step further in requiring that agents communicate only through HTTPS port (HTTP port is locked). This ensures that the OMS-Agent communication is always encrypted and mutually authenticated. All requests from un-secure agents are rejected by the OMS. Similarly, any un-secure request from the OMS is rejected by the agent. This helps safeguard the management system from any malicious ’man-in-the-middle' attack happening from within the infrastructure.
If your installation was done before Oracle Enterprise Manager 10g Release 5, you may be required to secure-lock your OMS manually. In the case of upgrades, if the pre-upgrade environment is secured, the upgrade retains the secure mode but does not secure-lock the OMS. If the pre-upgrade environment is already secure-locked, the upgrade retains the secure-lock mode between OMS and Agent.
To check the secure status of the OMS and secure-lock the communication between OMS and agent run the command and restart the OMS:
$ emctl status oms –details Oracle Enterprise Manager Cloud Control 12c Release 188.8.131.52.0 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved. Enter Enterprise Manager Root (SYSMAN) Password : Console Server Host : mgmthost.acme.com HTTP Console Port : 7790 HTTPS Console Port : 7803 HTTP Upload Port : 4890 HTTPS Upload Port : 4904 OMS is not configured with SLB or virtual hostname Agent Upload is locked. OMS Console is locked. Active CA ID: 1 Console URL: https://mgmthost.acme.com:7803/em Upload URL: https://mgmthost.acme.com:4904/empbs/upload … $ emctl secure lock –upload Oracle Enterprise Manager Cloud Control 12c Release 184.108.40.206.0 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved. Enter Enterprise Manager Root (SYSMAN) Password : Agent Upload is locked. Agents must be secure and upload over HTTPS port. Restart OMS.
Note that once OMSs are running in secure-lock mode, unsecure agents will not able to upload any data to the OMSs. To check the status and secure the agent issue the following, you will be prompted for the registration password:
$ emctl status agent –secure Oracle Enterprise Manager 12c Cloud Control 220.127.116.11.0 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved. Checking the security status of the Agent at location set in /scratch/cllamas/oracle/em12/agent/agent_inst/sysman/config/emd.properties... Done. Agent is secure at HTTPS Port 3872. Checking the security status of the OMS at https://mgmthost.acme.com:4904/empbs/upload/... Done. OMS is secure on HTTPS Port 4904 $ emctl secure agent Oracle Enterprise Manager 12c Cloud Control 18.104.22.168.0 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved. Agent successfully stopped... Done. Securing agent... Started. Enter Agent Registration Password : Agent successfully restarted... Done. EMD gensudoprops completed successfully Securing agent... Successful.
To ensure the console access from the client browser is secure over SSL/TSL, the console must be locked as well. From Oracle Enterprise Manager 10g Release 5 installations are secure-locked by default. In the case of upgrades, if the pre-upgrade environment is not secure-locked, after the upgrade you need to run the following command to secure-lock the console access:
$ emctl secure lock –console
A cipher suite is a combination of cryptographic parameters that define the security algorithms and key sizes used for authentication, key agreement, encryption, and integrity protection. Cipher suites protect the integrity of a communication. For example, the cipher suite called RSA_WITH_RC4_128_MD5 uses RSA for key exchange, RC4 with a 128-bit key for bulk encryption, and MD5 for message digest. Enterprise Manager allows strong cipher suites for the communication between OMS and agent. By default, the following cipher suites will be allowed for the communication on the agent:
To see the current Cipher Suites enabled view the Agent properties in the Enterprise Manager Console or run:
$ emctl getproperty agent -name SSLCipherSuites Oracle Enterprise Manager 12c Release 1 22.214.171.124.0 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved. SSLCipherSuites is unset; default value is SSL_RSA_WITH_RC4_128_MD5:SSL_RSA_WITH_RC4_128_SHA:SSL_RSA_WITH_3DES_EDE_CBC_SHA:SSL_RSA_WITH_DES_CBC_SHA:SSL_RSA_EXPORT_WITH_RC4_40_MD5:SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
To configure the strong cipher suites to be used for agent SSL/TLS communication edit the Agent properties in the Enterprise Manager Console or use the setproperty command:
$ emctl setproperty agent -name SSLCipherSuites -value <values>
The following are supported strong cipher suites:
To restrict the strong cipher suites used by OMS, please edit SSLCipherSuite parameter in $INSTANCE_HOME/WebTierIH1/config/OHS/ohs1/httpd_em.conf and ssl.conf files with the appropriate values. Here are the default values:
Use a certificate from well-known Certificate Authority (CA) to secure OMS-Agent communication and console access to take advantage of the well-known trusted certificates with different expiry and key size.
An Oracle wallet is a password-protected container used to store authentication and signing credentials, including private keys, certificates, and trusted certificates needed by SSL.
To secure the console using a custom certificate authority, you must create a wallet location and secure the console against that wallet location. For more information on creating a wallet, see the Oracle Fusion Middleware Administrator's Guide.
The following example shows how to create a self-signed certificate that can be used in secure communication with Oracle Enterprise Manager.
Create the wallet container:
Note:Currently, only single sign-on (SSO) wallets are supported.
S /u01/app/oracle/middleware/oracle_common/bin/orapki wallet create -wallet /home/oracle/labs/mywallet -auto_login_only
Add a certificate to the wallet: When creating the wallet you must specify the Common Name (CN) as the hostname of the machine where the OMS is installed or the SLB name, if the OMS is behind an SLB. In this example, the OMS is behind an SLB, test.example.com.
S /u01/app/oracle/middleware/oracle_common/bin/orapki wallet add -wallet /home/oracle/labs/mywallet -dn 'CN=test.example.com, OU=Oracle, O=Department, L=Boise, ST=ID, C=US' -keysize 2048 -self_signed -validity 3650 -auto_login_only
Set the required environment variables:
$ . setDomainEnv.sh
View the certificates in the wallet:
S /u01/app/oracle/middleware/oracle_common/bin/orapki wallet display -wallet /home/oracle/labs/mywallet
Here is a summary of the best practices for securing communication:
• Enable ICMP for ping check validation
• Configure firewalls as appropriate in your environment
• Secure and lock the OMS and Agents
• Configure strong cipher suites for the OMS and Agent
• Secure upload and console virtual HTTPS hosts with third party certificates
Enterprise Manager Cloud Control 12c offers multiple methods of authentication. In addition to the predefined methods, a customized provider/module can be plugged in to Cloud Control authentication. The default system authentication method is the standard Repository based authentication. Additional predefined methods include:
Oracle Single Sign-On (OSSO)
Enterprise User Security (EUS)
Integration with Oracle Access Manager Single Sign-On (OAM SSO)
Direct LDAP integration (Oracle Internet Directory, Microsoft Active Directory)
Refer to "Configuring Authentication" for detailed information about how to configure Enterprise Manager to use the pre-defined providers.
Using one of the extended authentication modules enables you to take advantage of centralized identity management across the enterprise. Doing this allows you to rely on the external identity management system for password security compliance, password changes and resets. To create a user in Enterprise Manager with external authentication, you select the ”external” flag upon creation. During creation of every new user in Enterprise Manager you are prompted for that users mode of Authentication, via an external Identity store such as Oracle Access Manager (OAM), LDAP or Oracle Internet Directory (OID), or internally via Enterprise Manager Repository. The following figure shows the default window which appears during user creation.
When the account is deleted from the identity management system, it will no longer authenticate in Enterprise Manager but still needs to be manually removed. Ideally, a script or job could be run to remove the user from Enterprise Manager once removed from the identity management system.
When using external Authentication, Enterprise Manager allows the creation of external roles which map to the identity management systems groups by name (i.e. Enterprise Manager role ”DBA” maps to LDAP group ”DBA”). Thus allowing synchronized user access and privileges based on external group membership.
Target authentication provides access to the host, database or application targets managed through Enterprise Manager. Using strong target authentication methods, named credentials and configuring database password profiles are a few ways to ensure secure target authentication.
To ensure target authentication security, choose strong host and database authentication methods. Credentials for target access are encrypted and stored in Enterprise Manager. With Enterprise Manager Cloud Control 12c, strong authentication such as SSH-keys for host and Kerberos tickets for database are now supported. These credentials can be used by jobs, deployment procedures and other subsystems.
Integrate with corporate identity management system for enterprise wide authentication
Use external roles to automatically assign privileges to users based on external group membership
Automate user creation/deletion based on external group membership using EMCLI
Utilize strong authentication methods (SSH for host, Kerberos for database)
For local accounts set up password policies
Authorization is the act of validating the privileges and permissions of an authenticated subject. To avoid exploiting authorization, you must implement a policy of segregation of duties. This means no one person should be given responsibility for more than one related function.
Enterprise Manager users may vary widely among a company, and they may have very different roles and purposes.
Enterprise Manager 12c comes with several out-of-the-box roles that provide role based authentication for various operational roles. Segregation of Operator, Designer and Administrator functions for Patching, Provisioning, Cloud, Compliance, and Plug-ins allow more granular authentication for users. Use the Create Like feature to further enhance or restrict as required for your operations.
Note:Performing a Create Like operation on an existing role enables the newly created role to contain all of the privileges of the original role.
With using Role Based Access Control (RBAC), privilege management becomes easier; managing role grants is simpler than managing privilege grants. For a complete list of the out-of-the-box roles see the Privileges and Roles section of the Oracle Enterprise Manager Cloud Control Administrator's Guide.
With Enterprise Manager 12c we have the ability to specify target privileges and resource privileges. Target privileges allow an administrator to perform operations on a target. Some of the new target privileges include Connect to any Viewable Target, Execute Command Anywhere, Execute Command as any Agent and more. The target privileges can be assigned for all targets or for specific targets. Resource privileges grant access to a function, button or page within Enterprise Manager. Some of the new resource privileges include Backup Configurations, Cloud Policy, Compliance Framework, Enterprise Manager Plug-in, Job System, Patch Plan, Self Update and Template Collection. For a complete list, see "Configuring Privileges and Role Authorization". With these new privileges, it's much easier to implement the Principal of Least Privilege by creating specific roles with very fine grained privileges assigned that match the job duties.
An extended auditing system makes it easy to monitor the privilege grants on a regular basis and also keep track of which users exercised what privileges. Some of the key privilege related auditable actions are listed here:
Grant job privilege
Grant target privilege
Grant system privilege
Revoke job privilege
Revoke target privilege
Revoke system privilege
Super Administrators have FULL privileges on targets/reports/templates/jobs. These are the only users who can create other users and Super Administrators, and grant/revoke privileges to/from other users. Super Administrator privilege should be granted with caution. Using the following query to get the list of Super Administrators:
SELECT grantee FROM MGMT_PRIV_GRANTS WHERE PRIV_NAME = ’SUPER_USER'
Create meaningful roles and grant roles to users instead of granting privileges to users.
Grant only the minimum set of privileges a user needs for carrying out his/her responsibilities by granting the fine-grained privileges/roles only when needed.
Audit privilege and role actions for complete monitoring and accountability.
Limit the number of Super Administrators
The fine granularity of privileges provided in Enterprise Manager allows for the Principle of Least Privileges to be implemented, this recommends that an Administrator must only be able to access the information or resources that are necessary for legitimate purposes.
Using groups and systems to organize your targets helps reduce security administration overhead. There are two types of groups available in Enterprise Manager 12c that help simplify privilege management and authorization. By granting roles to groups, instead of users and using privilege propagating groups, you can reduce the direct grants and ensure users have access to the targets as needed.
Privilege Propagating Groups simplify the privilege assignment, revocation, and administration along with group management by propagating the assigned privileges to all members of the group. For example, a user can be granted access to a privilege propagating group Sales, and they in turn receive access to all targets within that group.
Administration Groups are privilege propagating groups that automate the application of monitoring settings to targets upon joining the group. Targets cannot be assigned directly to the group, rather they are automatically added based on membership criteria.
Systems are also privilege propagating and allow you to group all related targets of a particular application or function into a system.
Create meaningful roles and grant roles to users instead of granting privileges to users.
Grant only the minimum set of privileges a user needs for carrying out his/her responsibilities by granting the fine-grained privileges/roles only when needed.
Utilize privilege propagating groups and systems to reduce administration overhead
Enterprise Manager has additional auditing that is available for purposes of tracking and validating infrastructure actions performed in Enterprise Manager, including jobs and credentials accessed. Basic and infrastructure auditing is enabled by default for Enterprise Manager 12c.
To enable audit for a subset of audited operations, please use the following EMCLI verb:
$ emcli update_audit_settings -audit_switch="ENABLE/DISABLE" -operations_to_enable="name of the operations to enable,for all operations use ALL" -operations_to_disable="name of the operations to disable, for all operations use ALL"
For example to audit only logon/logoff you would issue:
$ emcli update_audit_settings –audit_switch=”ENABLE” –operations_to_enable=”LOGIN;LOGOUT”
Refer to the section "Configuring and Managing Audit" for the list of operations that are audited by Enterprise Manager.
In Enterprise Manager 12c, there are over 150 options for auditing. The following command will show you the list of operations that can be audited by Enterprise Manager:
$ emcli show_operations_list
The following example shows the output of this command.
$ ./emcli show_operations_list Operation ID Operation Name Infrastructure Operation ADD_AGENT_REGISTRATION_PASSWORD Add Registration Password NO ADD_CS_TARGET_ASSOC Add Standard-Target Association NO AGENT_REGISTRATION_PASSWORD_USAGE Registration Password Usage NO AGENT_RESYNC Resync Agent NO AG_AUD_CREATE Create Administration Groups NO AG_AUD_DELETE Delete Administration Groups NO AG_AUD_MODIFY Modify Administration Groups NO APPLY_TEMPLATE Apply Monitoring Template NO APPLY_UPDATE Apply Update YES ATTACH_MEXT Attach Metric Extension NO
Once audit is enabled, the audit records are kept in MGMT$AUDIT_LOG view in the Repository. Use Enterprise Manager Cloud Control Console to monitor the audit data as user with Super Administrator, click Setup -> Security -> Audit Data.
The externalization service via EMCLI verb update_audit_settings externalizes the audit data from the Repository to an external file system on a regular basis. Make sure there is enough space in the directory for the audit log files.
$ emcli update_audit_settings -file_prefix=<file_prefix> -directory_name=<directory_name> -file_size = <file size> -data_retention_period=<period in days>
The following example shows that the audit data will be retained in the Repository for 14 days and once exported the data will be stored in the OS directory that corresponds to database directory AUDIT with filenames prefixed with gc12_audit, and the file size will be 50M bytes each:
$ emcli update_audit_settings -externalization_switch=ENABLE -file_prefix=gc12_audit -directory=AUDIT -file_size=50000000 -data_retention_period=14
Achieve separation of duties by restricting the access to the directory where the externalized audit data is stored. No Enterprise Manager users should have access to the externalized audit data.
Preferred Credentials simplify access to managed targets by storing target login credentials in the Management Repository. Users can access an Enterprise Manager target that recognizes those credentials without being prompted to log into the target. Preferred credentials are set on a per user basis, thus ensuring the security of the managed enterprise environment. Default credentials can be set for a particular target type as well as target credentials for a particular target. The target credentials override the default credentials.
Do not set preferred credentials for group/common accounts such as SYSMAN. If preferred credentials are set for common accounts, then the accountability of the use of these credentials is lost. The following SQL statements can be used to report the list of users who have the preferred credentials set:
SELECT t.target_name,tc.user_name,tc.credential_set_name FROM MGMT_TARGET_CREDENTIALS tc, MGMT_TARGETS t WHERE tc.target_guid=t.target_guid SELECT t.target_name,tc.user_name, tc.set_name FROM EM_TARGET_CREDS tc, MGMT_TARGETS t WHERE tc.target_guid=t.target_guid and tc.user_name = 'SYSMAN'
Credentials can be stored as Named Credentials and then privileges granted to other users to use, update or own the credentials. These credentials can be used for jobs, patching or other administration tasks on specific targets or globally. Eligible credential types include username/password, SSH-key for host and Kerberos for database. This method allows administrators to configure Named Credentials for privileged access and grant to specific users. Auditing tracks Named Credential creation, modification and usage.
Named Credentials provide a secure mechanism in Enterprise Manager to allow for separation of privilege management from privilege delegation for targets. Using Named Credentials an organization can separate the management of the specific username/password/authentication details from the actual authority to use these credentials. This is an essential tool in modern, secure organizations where there needs to be certainty that a malicious user cannot conduct operations outside Enterprise Manager using a set of known credentials obtained from inside Cloud Control. Additionally, the management of a central set of Named Credentials removes a significant burden on the proliferation of credentials information across many Enterprise Manager administrators and also therefore reduces the likelihood of these being used outside the Enterprise Manager environment or helps prevent against the accidental publication of credentials.
Use EMCLI to automate routine password changes on privileged named credentials, this allows one administrator to know and update the password for granted users.
Utilize named credentials when setting preferred credentials to simplify credential management.
Do not set preferred credentials for group/common accounts such as SYSMAN.