Securing
This section describes security features, including execution control lists, IDs, and TLS.
- Overview of Domino security
  Setting up security for your organization is a critical task. Your security infrastructure is critical for protecting your organization's IT resources and assets. As an administrator, you need to give careful consideration to your organization's security requirements before you set up any servers or users. Up-front planning pays off later in minimizing the risks of compromised security.
- Server access for Notes® users, Internet users, and Domino® servers
  To control user and server access to other servers, Domino® uses the settings you specify on the Security tab in the Server document as well as the rules of validation and authentication. If a server validates and authenticates the Notes® user, Internet user, or server, and the settings in the Server document allow access, the user or server is allowed access to the server.
- The database access control list
  Every .NSF database has an access control list (ACL) that specifies the level of access that users and servers have to that database. Although the names of access levels are the same for users and servers, those assigned to users determine the tasks that they can perform in a database, while those assigned to servers determine what information within the database the servers can replicate. Only someone with Manager access can create or modify the ACL.
- Domino® server and Notes® user IDs
  Domino® uses ID files to identify users and to control access to servers. Every Domino server, Notes® certifier, and Notes user must have an ID.
- The execution control list
  You use an execution control list (ECL) to configure workstation data security. An ECL protects user workstations against active content from unknown or suspect sources, and can be configured to limit the action of any active content that does run on workstations.
- Domino® server-based certification authority
  You can set up a Domino® certifier that uses the CA process server task to manage and process certificate requests. The CA process runs as a process on Domino servers that are used to issue certificates. When you set up a Notes® or Internet certifier, you link it to the CA process on the server in order to take advantage of CA process activities. Only one instance of the CA process can run on a server; however, the process can be linked to multiple certifiers.
- TLS security
  Transport Layer Security (TLS) is a security protocol that provides communications privacy and authentication for Domino® server tasks that operate over TCP/IP.
- TLS and S/MIME for clients
  Clients can use a Domino® certificate authority (CA) application or a third-party CA to obtain certificates for secure TLS and S/MIME communication.
- Encryption
  Encryption protects data from unauthorized access.
- Name-and-password authentication for Internet/intranet clients
  Name-and-password authentication, also known as basic password authentication, uses a basic challenge/response protocol to ask users for their names and passwords and then verifies the accuracy of the passwords by checking them against a secure hash of the password stored in Person documents in the Domino® Directory.
- Time-based one-time password (TOTP) authentication
  When users log on to a Domino Web server, you can require that they provide time-based one-time passwords in addition to their user names and passwords.
- Multi-server session-based authentication (single sign-on)
  Multi-server session-based authentication, also known as single sign-on (SSO), allows Web users to log in once to a Domino® or WebSphere® server, and then access any other Domino or WebSphere servers in the same DNS domain that are enabled for single sign-on (SSO) without having to log in again.
- Using Security Assertion Markup Language (SAML) to configure federated-identity authentication
  Federated identity is a means of achieving single sign-on, providing user convenience and helping to reduce administrative cost. In Domino® and Notes®, federated identity for user authentication uses the Security Assertion Markup Language (SAML) standard from OASIS.
- Using OpenID Connect (OIDC) to configure federated-identity authentication
  Federated identity is a means of achieving single sign-on, providing user convenience and helping to reduce administrative cost. One way that client applications can authenticate users is by using an OpenID Connect (OIDC) provider.
- Using a credential store to store credentials
  A Domino® server can use a credential store application as a secure artifact repository. Examples of secure artifacts include authentication credentials and security keys.
- History of supported key sizes in Notes and Domino
  Understand the RSA key sizes supported by Notes® and Domino® from past releases to the current release.
  - The evolution of Notes RSA key sizes

The evolution of Notes RSA key sizes

Due to export restrictions, Notes ID files have always contained two RSA key pairs, one for "Domestic" use, and one for "International" use. The domestic key was used when domestic versions of Notes communicated with each other, and the weaker international keys were used when an international version of Notes is involved. Signing was an exception, as the export restrictions primarily applied to keys used to provide secrecy for user-generated data. The International keys have been obsolete since the US Government eliminated the export restrictions in the 5.0.3 timeframe. Since clients and servers before R6 cannot interoperate with users with 1024+ bit RSA keys, we could safely eliminate the international key pair from those ID files with larger RSA keys. Due to the storage formats used in the ID file, both the domestic and the international keys point to the same key pair.

R6 generated 630 bit domestic keys and 512 bit international keys
R6 supported 1024 bit domestic keys* and 512 bit international keys
Support to generate flat ID files was removed from R6.
V4 and R5 generated 630 bit domestic keys and 512 bit international keys
V4 and R5 supported 760 bit domestic keys** and 512 bit international keys
V4 and R5 supported a maximum of 630 bit keys in flat ID files
Support to generate flat ID files was removed from R5.
V3 generated 512 bit domestic and international keys for hierarchical IDs
V3 generated 512 bit domestic and 380 bit international keys for flat IDs for compatibility with R2.
V3 supported 760 bit public keys and 630 bit private keys in hierarchical ID files.***
V3 supported 630 bit keys in flat ID files
V2.1 generated 512 bit domestic keys and 380 bit international keys (flat only)
V2.1 accepted 512 bit domestic keys and 512 bit international keys (flat only)
V1 and 2.0 could generate up to 512 bit domestic keys and 380 bit international keys. (flat only)
V1 and 2.0 accepted 512 bit domestic keys and 380 bit international keys. (flat only)

* RSA Keys over 630 bits must be BER-formatted.

** V4 and R5 do not support BER-formatted keys.

*** Since keys between 630 and 760 bits in length have never been used, this distinction is mostly academic.