15.2.34.R.02. Rationale
Having a proper Sender Policy Framework (SPF) record increases the chances people will get emails you send. Without one, your email has a
greater chance of being marked as Spam.
15.2.34.R.03. Rationale
SPF and alternatives such as Sender ID aid in the detection of spoofed email server address domains. The SPF record specifies a list of IP
addresses or domains that are allowed to send mail from a specific domain. If the email server that transmitted the email is not in the list, the
verification fails (there are a number of different fail types available).
15.2.34.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1792]
Agencies MUST:
specify mail servers using SPF or Sender ID; and
mark, block or identify incoming emails that fail SPF checks for notification to the email recipient.
15.2.34.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1793]
Agencies SHOULD:
use a hard fail SPF record when specifying email servers; and
use SPF or Sender ID to verify the authenticity of incoming emails.
15.2.34.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1794]
Agencies SHOULD refer to the SPF recommendations in IETF’s RFC 4408.
15.2.35. DomainKeys Identified Mail (DKIM)
15.2.35.R.01. Rationale
DKIM enables a method of determining spoofed email content. The DKIM record specifies a public key that will sign the content of the message.
If the signed digest in the email header doesn't match the signed content of the email the verification fails.
15.2.35.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1798]
Agencies SHOULD enable DKIM signing on all email originating from their domain.
15.2.35.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1797]
Agencies SHOULD use DKIM in conjunction with SPF.
15.2.35.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1799]
Agencies SHOULD verify DKIM signatures on emails received, taking into account that email distribution list software typically invalidates DKIM
signatures.
15.2.35.C.04. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1800]
Where agencies operate email distribution list software used by external senders, agencies SHOULD configure the software so that it does not
impair the validity of the sender’s DKIM signature.
16. Access Control and Passwords
16.1. Identification, Authentication and Passwords
Objective
16.1.1. Identification and authentication requirements are implemented in order to provide a secure means of access to information and systems.
Context
Scope
16.1.2. This section provides information on the identification and authentication of all system users.
16.1.3. Access Control is any mechanism by which an individual, system or application grants or revokes the right to access some location, system, data, or
perform some action. Access Control must be supported by an appropriate organisational policy.
16.1.4. In this context a user is a real person. Machine or device to device communication and interaction will also require authentication. It is important to
note, however, that the usual mechanisms applied to real persons cannot always be used in device to device authentication, for example, biometrics
cannot be used.
16.1.5. In Information Technology, a user will usually register a person’s identity supported by some evidence of identity (Eol). This will be accompanied by an
authority or approval to access information, usually from a manager or other executive. The authentication system will then issue credentials, usually
user ID and password, but may also include tokens or use biometrics. The credentials are the means by which a user (a person) accesses an
information technology system and are verified each time a user logs onto a system.
16.1.6. Access Control systems manage access rights, including:
Physical access to locations;
File system permissions, including physical documents and files, such as create, read, edit or delete data;
Program permissions, such as the right to execute a programme;
205
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents