Security

IBM Sterling Order Management Software

Security is an important consideration when configuring Sterling Order Management.
The collection of topics introduces the Sterling Order Management security concepts.
 Planning for security
 Planning for secure deployment
 DIME and DARE security considerations
 Implementing the PA-DSS
 Security planning - Java protocol security measures
As with the usage of any protocol technology there are certain associated risks.
 Web security planning
It is highly recommended that a security audit is made prior to deployment, and log files
are written to several servers.
 Database security
Set up separate accounts on the database server for installing the Sterling Selling and
Fulfillment Foundation schema and for accessing the application database.
 Updating to FIPS 140 security standards
Federal Information Processing Standards (FIPS) are standards and guidelines that are
issued by the National Institute of Standards and Technology (NIST) for federal
government computer systems. Federal Information Processing Standards publication
140-2 (FIPS 140-2) covers the security standards that are required for cryptographic
modules.
 Adding Sterling Selling and Fulfillment Foundation as a trusted web site
Set Sterling Selling and Fulfillment Foundation to be recognized as a trusted Web site.
Otherwise, it might result in certain pop-up windows such as date and time selection to
display a status bar, thereby hiding certain the action buttons.
 Securing elasticsearch servers
In a sharded OMS system, orders and shipments that are placed online, at a call center or
at stores can be stored in different database shards. The OMS uses a centralized search
index to efficiently find orders or shipments across the shards. An order or shipment
search in OMS results in a request to the search engine, which will return a list of shards,
identified by Colony IDs, that contain the orders or shipments. OMS will then search the
appropriate shards in parallel. The OMS search index uses an open source project called
elasticsearch, which is based on top of Apache Lucene.

Security - planning your deployment

architecture
Last Updated: 2021-04-16
Prior to procuring and implementing the hardware and software that make up Sterling Selling
and Fulfillment Foundation, you need to plan your deployment architecture.

To plan your deployment architecture, complete the following tasks:

  Conduct an analysis of the current security infrastructure in your organization.

 Conduct an analysis of authentication and authorization mechanisms in your organization

to identify the steps needed to incorporate them into Sterling Selling and Fulfillment
Foundation.
 Conduct an analysis of your data encryption mechanisms for deploying Sterling Selling
and Fulfillment Foundation over the internet.
 Conduct an analysis of your organization's network topology required to deploy Sterling
Selling and Fulfillment Foundation.

Completing these tasks enables you to:

 Estimate your server requirements.

 List the major security software and hardware needed to implement Sterling Selling and
Fulfillment Foundation.
 Security planning - current security infrastructure analysis
In order to ensure that your Sterling Selling and Fulfillment Foundation is a secure Web
application, there are many factors involved.
 Security planning - authentication and authorization
Authentication and authorization are vital to security. Due to the constantly changing
authentication methodologies, including biometrics, public key infrastructure (PKI), and
ever-increasing encryption algorithms, Sterling Selling and Fulfillment
Foundation provides documentation on implementing a lightweight directory access
protocol (LDAP) or any Java™ Authentication and Authorization Service (JAAS)
compliant security module for authentication.
 Security planning - data encryption
Due to the differences in the nature of businesses, you may implement different security
measures when implementing a web application. How you plan to deploy the application
and what security measures are taken are unique to each business.
The data encryption mechanisms recommended for Sterling Selling and Fulfillment
Foundation are:

 SSL - 128-bit encryption is the recommended encryption level.

 VPN - 3DES or AES is the recommended encryption algorithm.

 Security planning - network topology

Sterling Selling and Fulfillment Foundation is typically implemented as an internal
application that is accessible from an Internal Network or across from VPN.

Web security planning

Last Updated: 2021-04-16
It is highly recommended that a security audit is made prior to deployment, and log files are
written to several servers.

There are several applications that do this with no specific need for Sterling Selling and
Fulfillment Foundation to duplicate their efforts. Additionally, products like Symantec's Intruder
Alert monitor log files for authentication failures and alert an administrator if a threshold is
exceeded.
 Web security planning - post-installation recommendations
After the installation of Sterling Selling and Fulfillment Foundation, you muse complete
the post-installation recommendations for ensured security.
 Web security planning - session security
Session security is handled by the application server, and is stored in a non-persistent
cookie on the client. You should ensure that all transactions with the application server
are protected with SSL to prevent session hijacking attacks.
 Web security planning - operating system permissions
Files that contain confidential information must be secured through operating system
permissions.
 Web security planning - documentation
All the documentation files for Sterling Selling and Fulfillment Foundation and third-
party software must be removed from any production servers.
 Web security planning - routing
Routing should not be enabled on a production web server.
 Web security planning - web server executables
Web servers should not be run as root. This ensures that if someone compromises any
software associated with the deployment through a bug, they don't have root privileges to
damage the server.

Database security - credit card encryption

Last Updated: 2021-04-16

If you want to ensure that credit card numbers are encrypted at the database level, you configure
that functionality when setting Hub attributes in the Applications Manager. When setting Hub
attributes, make sure that the credit card number encrypting option is checked.

DIME and DARE security considerations

Last Updated: 2021-04-16

This topic provides security recommendations and guidelines for setting up Data In Motion
Encryption (DIME) and Data At Rest Encryption (DARE). It is intended to help you create a
secure implementation of the application.
Data in motion encryption
Security considerations for data in motion encryption is as follows:

 SFTP support in SDF

File transfer protocol (FTP)

Last Updated: 2021-04-16

The FTP node allows for sending and receiving files. Files residing in a local directory are sent
to a remote directory on an FTP server. Files residing in a remote directory are received from an
FTP server and stored in a local directory. FTP node also provides support for SFTP (SSH File
Transport Protocol).

Note: Ensure that all source and destination directories and files have read/write permissions for
the remote user specified and for the user running the Integration Server.
Note: The FTP server is not multi-threaded.

 FTP sender
The properties of this node are described.
 FTP receiver
The properties of this node are described.

 JDBC encryption

JDBC encryption
Last Updated: 2021-04-16

You can set up JDBC encryption between following applications so that your data can be sent
securely over the network.

 WebSphere application server and DB2

 Agent or integration server and DB2

To set up JDBC encryption between WAS, agent or integration server and DB2, do the
following configurations:

 Configuring DB2 for Secure Sockets Layer (SSL)

Using Secure Sockets Layer (SSL) with IBM® DB2® means your data can be sent
securely over the network.
 Importing Secure Sockets Layer (SSL) certificates to WebSphere
WebSphere® Application Server uses the certificates that reside in keystores to establish
trust for a Secure Sockets Layer (SSL) connection. Since the DB2 port for IBM Sterling
 Order Management will be set to the secure port, therefore Websphere also should be
able to trust the DB2 certificate.
 Enabling Secure Sockets Layer (SSL) on data source in WebSphere
To enable SSL on data source perform the following steps:
 Configuring Sterling Order Management for Secure Sockets Layer (SSL) on DB2
and WebSphere
After enabling SSL on DB2 and WebSphere, you need to configure Sterling Order
Management for SSL support.

Data at rest encryption

Security considerations for data at rest encryption is as follows:

 DB2 encryption
DB2® encryption encrypts your DB2® database. It does not require hardware, software,
application, or schema changes. It provides transparent and secure key management.

In an encryption scheme, the data requiring protection is transformed into an unreadable form by
applying a cryptographic algorithm and an encryption key. A cryptographic algorithm is a
mathematical function that is used in encryption and decryption processes. An encryption key is a
sequence that controls the operation of a cryptographic algorithm and enables the reliable
encryption and decryption of data.

 Property encryption
Property encryption ensures that sensitive data is not viewed by unauthorized people. The
application provides APIs that enable you to encrypt data such as user names, passwords,
and credit card numbers.

Property encryption
Last Updated: 2021-04-16

Property encryption ensures that sensitive data is not viewed by unauthorized people. The
application provides APIs that enable you to encrypt data such as user names, passwords, and
credit card numbers.

The property encryption and decryption is applied only after it has been specified in the
Applications Manager. For example, only user exits that have been passed credit card
information can access decrypted credit card numbers.

 How Is transactional data secured?

Security issues involve controlling who has access to what data, how much they can see,
and what they can do with it.
  Encryption logic
The application exposes the com.yantra.ycp.japi.util.YCPEncrypter interface to handle
encryption logic. All application encryption and decryption is handled by an encrypter
class that implements this interface.
 How is encryption supported?
There are many ways in which encryption is supported.
 Encryption through property files
Some properties relay sensitive data such as user IDs and passwords, which you may
want to encrypt.

 Encrypting data partitions using LUKS

To encrypt a Linux partition using Linux Unified Key Setup (LUKS).
 JDBC encryption
You can set up JDBC encryption between following applications so that your data can be
sent securely over the network.

To set up JDBC encryption between WAS, agent or integration server and DB2, do the
following configurations:

 Configuring DB2 for Secure Sockets Layer (SSL)

Using Secure Sockets Layer (SSL) with IBM® DB2® means your data can be sent
securely over the network.
 Importing Secure Sockets Layer (SSL) certificates to WebSphere
WebSphere® Application Server uses the certificates that reside in keystores to establish
trust for a Secure Sockets Layer (SSL) connection. Since the DB2 port for IBM Sterling
Order Management will be set to the secure port, therefore Websphere also should be
able to trust the DB2 certificate.
 Enabling Secure Sockets Layer (SSL) on data source in WebSphere
To enable SSL on data source perform the following steps:
 Configuring Sterling Order Management for Secure Sockets Layer (SSL) on DB2
and WebSphere
After enabling SSL on DB2 and WebSphere, you need to configure Sterling Order
Management for SSL support.