Personnel guidelines for avoiding phishing

Critical
High
Normal
Low

The organization has developed guidelines for staff that define the acceptable use of various communication services and aim to prevent the disclosure of confidential information to, for example, a phisher or other third parties.

Connected other frameworks and requirements:
13.2.1: Information transfer policies and procedures
ISO 27001
13.2.3: Electronic messaging
ISO 27001
PR.AT-1: Awareness
NIST CSF
5.14: Information transfer
ISO 27001

Email authentication: DMARC

Critical
High
Normal
Low

SPF, DKIM and DMARC are technologies that prevent the sending of fake emails and phishing.

DMARC works together with SPF and DKIM. It tells the receiving e-mail server how to deal with a message that do not pass SPF or DKIM checks.

Connected other frameworks and requirements:
13.2.3: Electronic messaging
ISO 27001
5.14: Information transfer
ISO 27001

Email authentication: DKIM

Critical
High
Normal
Low

SPF, DKIM, and DMARC are technologies that prevent the sending of fake emails and phishing.

DKIM adds a digital signature to the header of outgoing e-mail. The outgoing e-mail header is encrypted with a private key, and the public key is added to the domain's DNS information so that the receiving server can decrypt the information. The key therefore ensures that the messages actually come from your own domain and not from the sender impersonating you.

Connected other frameworks and requirements:
13.2.3: Electronic messaging
ISO 27001
5.14: Information transfer
ISO 27001

Email authentication: SPF

Critical
High
Normal
Low

SPF, DKIM, and DMARC are technologies that prevent the sending of fake emails and phishing.

Using SPF will help verify the authenticity of emails sent from your domain. The SPF is added as a TXT entry to your domain's DNS information to tell you which email servers are allowed to send email on behalf of your domain. The receiving email server refers to this entry when deciding whether the email is coming from the right party.

Connected other frameworks and requirements:
13.2.3: Electronic messaging
ISO 27001
5.14: Information transfer
ISO 27001

Enabling and configuring mailbox audit logs

Critical
High
Normal
Low

With the mailbox audit logs, it is possible to track, for example, logins and other actions within inbox.

Usually, this feature is not turned on by default, and for employee privacy, it is important to choose the actions to be monitored carefully.

Connected other frameworks and requirements:
13.2.3: Electronic messaging
ISO 27001
5.14: Information transfer
ISO 27001

Encryption of public network traffic for application services

Critical
High
Normal
Low

Information included in application services transmitted over public networks must be protected against fraudulent and non-contractual activity and against unauthorized disclosure and alteration.

We use strong encryption and security protocols (eg TLS, IPSEC, SSH) to protect confidential information when it is transmitted over public networks in connection with the IT services we develop.

Connected other frameworks and requirements:
13.2.3: Electronic messaging
ISO 27001
14.1.2: Securing application services on public networks
ISO 27001
14.1.3: Protecting application services transactions
ISO 27001
14.2.5: Secure system engineering principles
ISO 27001
PR.DS-2: Data-in-transit
NIST CSF

Use of anti-phishing policies

Critical
High
Normal
Low

Anti-phishing policies can help an organization prevent impersonation-based phishing. Targeted “spear phishing” attacks in particular are often so skillfully executed that even a conscious employee finds it difficult to identify a scam.

For example, the ATP extension for Microsoft 365 can quarantine e-mail messages that impersonate our CEO or that present our own domain as the sender's domain, while forwarding them to the person in charge of security.

Connected other frameworks and requirements:
13.2.1: Information transfer policies and procedures
ISO 27001
13.2.3: Electronic messaging
ISO 27001
5.14: Information transfer
ISO 27001

Mailbox audit log monitoring

Critical
High
Normal
Low

Once the mailbox audit log is enabled, the events should be saved to a selected location for a desired time. This can be, for example, "Audit log search" in a Microsoft 365 environment or a separate SIEM system. In addition, it is necessary to decide on the control measures to be taken.

Connected other frameworks and requirements:
13.2.3: Electronic messaging
ISO 27001
5.14: Information transfer
ISO 27001

Email monitoring system

Critical
High
Normal
Low

With the help of email monitoring, e.g. identify personal, unstructured but valuable or sensitive personal or other information in e-mail traffic and the system.

Connected other frameworks and requirements:
13.2.3: Electronic messaging
ISO 27001
No items found.