3 Implementing OSM Security

This chapter provides a synopsis of the Order and Service Management (OSM) security features. For additional details, see the information about setting up OSM security in OSM System Administrator's Guide.

Secure Credential Management

OSM provides two distinct secure credential management solutions, each appropriate to the type of credential to be secured:

  • EncryptPasswords utility: This utility is used to secure the credentials required to run other OSM utilities, such as the XML Import/Export tool. Oracle recommends that you use it when you run utilities unattended. If you are running the utilities attended, Oracle recommends that you provide the required credentials interactively as the utility prompted by the utility, rather than using EncryptPasswords. If you are using EncryptPasswords, must to be possible to perform an automated transformation of the password. Because the transformation of the password is automated, the output of EncryptPasswords should be considered obfuscated rather than encrypted. Secure the files containing the output with appropriate file-system-level restrictions.

  • Credential Store: This utility is used to secure credentials required to access systems with which your OSM solution interacts. It builds on the Credential Store Framework (CSF), adding OSM-specific features.

For information about how to secure credentials using these methods, see OSM System Administrator's Guide.

Secure Solution Data Storage

As a fulfillment system, OSM does not need a fixed data model, and so is not required or typically used to store sensitive data other than that used for OSM user authentication.

You can secure OSM user credentials as described in "Secure Credential Management," but if your implementation requires OSM to store or log other sensitive data that appears on orders, Oracle recommends that you encrypt the data outside of OSM. Because the encryption happens outside of OSM, you are responsible for developing and maintaining the encryption method.

Using the WebLogic Scripting Tool

Several OSM features make use of the WebLogic Scripting Tool (WLST). When connecting to a WebLogic Server service instance, Oracle recommends that you connect to the service instance through the administration port. By default, this port is not enabled, but Oracle recommends that you enable the administration port in a production environment. The administration port requires all communication to be secured using SSL. By default, all servers in a WebLogic Server domain use demonstration certificate files for SSL, but these certificates are not appropriate for a production environment. For information about configuring the administration port, see the information about the administration port and administrative channel in Administering Server Environments for Oracle WebLogic Server. For more information about WLST, see Oracle Fusion Middleware Understanding the WebLogic Scripting Tool. For more information about connecting to WLST for OSM, see the information about managing and monitoring OSM in OSM System Administrator's Guide.

Secure Logging

OSM can be configured to suppress stack trace information in log output. A stack trace is a list of the method calls that an application is in the middle of at the time an exception is thrown. Running OSM with stack-trace logging enabled can be important for debugging the application during run time. However, in certain cases, suppressing this information can improve application security.

You can enable or disable logging stack traces using the oms-config.xml parameter enable_log_stacktraces. By default, this parameter is enabled. If there is a security concern about having log stack traces enabled, you can disable this parameter. For more information about setting this parameter, see the information about configuring OSM with oms-config.xml in OSM System Administrator's Guide.