Siebel Security Guide > About Security for Siebel Business Applications >

Industry Standards for Security

Siebel Business Applications adhere to common security standards to facilitate the integration of its applications into the customer environment. Siebel Business Applications are designed so that customers can choose a security infrastructure that best suits their specific business needs.

Supported standards include:

• Lightweight Directory Access Protocol (LDAP) and Active Directory Service Interfaces (ADSI). Siebel Business Applications provide preconfigured integration with LDAP and ADSI for user authentication purposes. For more information, see Security Adapters for LDAP and ADSI Authentication and Security Adapter Authentication.
• Communications encryption. Siebel Business Applications support the use of the following technologies for communications encryption:
  • Secure Sockets Layer (SSL) and Transport Layer Security (TLS) encryption and authentication. SSL or TLS can be used to protect communications between the following:
    • Siebel Business Applications components, that is, Siebel Servers and Web servers.
    • Siebel Web servers and Siebel Web Clients, if support for the protocol is provided by the Web server. The use of SSL or TLS for Web server and Siebel Web Client communications is transparent to Siebel Business Applications.
    • Siebel Servers and Microsoft Exchange Server email servers (SSL) or Siebel Servers and Microsoft Exchange Server 2007 or 2010 email servers (TLS).

      NOTE:  Oracle does not support the use of SSL v3.0 encryption for environments with high-security requirements. It is recommended that you implement TLS encryption where possible. For additional information, see Using Secure Socket Layer v3.0 with Siebel CRM.

      The following table lists topics that provide information on configuring SSL and TLS.

      Information Type	Topic
      Restricting access to specific views to URLs that use TLS.	Configuring a Siebel Web Client to Use HTTPS
      Configuring SSL or TLS for communication between Siebel components.	Process of Configuring Secure Communications
      Using SSL or TLS to secure user login credentials	Implementing Secure Login
      Using SSL or TLS to secure communications between Siebel Servers and directory servers.	Configuring Secure Communications for Security Adapters

  • RSA communications encryption. Communication between Siebel components can be encrypted using RSA encryption algorithms. For more information, see Process of Configuring Secure Communications.

    For supported UNIX operating systems, Windows operating systems, or cross-operating system environments, Siebel Business Applications support RSA BSAFE. RSA BSAFE is FIPS 140-1 certified.

  • Microsoft Crypto. For supported Windows operating systems, Siebel Business Applications support Microsoft Crypto. If the Siebel Server and the Web server are installed on the same computer running Microsoft Windows, then you cannot use Microsoft Crypto. You can use it only when these components run on different Microsoft Windows computers. For more information, see Process of Configuring Secure Communications and Types of Encryption.
• X.509 certificates. Siebel Business Applications use the TLS capabilities of supported Web servers to enable authentication based on X.509 client certificates. For more information, see About Digital Certificate Authentication.
• RSA SHA-1 password hashing. Siebel user passwords can be hashed using the RSA SHA-1 algorithm. For more information, see About Password Hashing.
• AES. Siebel data can be encrypted using Advanced Encryption Standard (AES). Multiple key lengths are supported for AES using Siebel Strong Encryption. For more information, see About Data Encryption.

NOTE:  Siebel Business Applications do not provide direct support for the Security Assertion Markup Language (SAML) standard.