Content library
ISO 27001 (2013): Full
13.2.3: Electronic messaging

Requirement description

How to fill the requirement

ISO 27001 (2013): Full

13.2.3: Electronic messaging

Task name
Priority
Status
Theme
Policy
Other requirements
Personnel guidelines for avoiding phishing
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Email and phishing
Email and web browser
9
requirements

Examples of other requirements this task affects

13.2.1: Information transfer policies and procedures
ISO27 Full
13.2.3: Electronic messaging
ISO27 Full
PR.AT-1: Awareness
NIST
HAL-12: Ohjeet
Julkri
5.14: Information transfer
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Personnel guidelines for avoiding phishing
1. Task description

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.

Email authentication: DMARC
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Email and phishing
Email and web browser
4
requirements

Examples of other requirements this task affects

13.2.3: Electronic messaging
ISO27 Full
5.14: Information transfer
ISO27k1 Full
2.8.1: Verify the sender address of incoming emails
NSM ICT-SP
See all related requirements and other information from tasks own page.
Go to >
Email authentication: DMARC
1. Task description

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.

Email authentication: DKIM
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Email and phishing
Email and web browser
4
requirements

Examples of other requirements this task affects

13.2.3: Electronic messaging
ISO27 Full
5.14: Information transfer
ISO27k1 Full
2.8.1: Verify the sender address of incoming emails
NSM ICT-SP
See all related requirements and other information from tasks own page.
Go to >
Email authentication: DKIM
1. Task description

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.

Email authentication: SPF
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Email and phishing
Email and web browser
4
requirements

Examples of other requirements this task affects

13.2.3: Electronic messaging
ISO27 Full
5.14: Information transfer
ISO27k1 Full
2.8.1: Verify the sender address of incoming emails
NSM ICT-SP
See all related requirements and other information from tasks own page.
Go to >
Email authentication: SPF
1. Task description

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.

Enabling and configuring mailbox audit logs
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Email and phishing
Email and web browser
2
requirements

Examples of other requirements this task affects

13.2.3: Electronic messaging
ISO27 Full
5.14: Information transfer
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Enabling and configuring mailbox audit logs
1. Task description

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.

Encryption of public network traffic for application services
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Development and cloud
Secure development
14
requirements

Examples of other requirements this task affects

13.2.3: Electronic messaging
ISO27 Full
14.1.2: Securing application services on public networks
ISO27 Full
14.1.3: Protecting application services transactions
ISO27 Full
14.2.5: Secure system engineering principles
ISO27 Full
PR.DS-2: Data-in-transit
NIST
See all related requirements and other information from tasks own page.
Go to >
Encryption of public network traffic for application services
1. Task description

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.

Use of anti-phishing policies
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Email and phishing
Email and web browser
4
requirements

Examples of other requirements this task affects

13.2.1: Information transfer policies and procedures
ISO27 Full
13.2.3: Electronic messaging
ISO27 Full
5.14: Information transfer
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Use of anti-phishing policies
1. Task description

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.

Mailbox audit log monitoring
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Email and phishing
Email and web browser
2
requirements

Examples of other requirements this task affects

13.2.3: Electronic messaging
ISO27 Full
5.14: Information transfer
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Mailbox audit log monitoring
1. Task description

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.

Email monitoring system
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Email and phishing
Email and web browser
2
requirements

Examples of other requirements this task affects

13.2.3: Electronic messaging
ISO27 Full
See all related requirements and other information from tasks own page.
Go to >
Email monitoring system
1. Task description

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.

Tasks included in the policy

Task name
Priority
Status
Theme
Policy
Other requirements
No items found.

Universal cyber compliance language model: Comply with confidence and least effort

In Cyberday, all frameworks’ requirements are mapped into universal tasks, so you achieve multi-framework compliance effortlessly.

Security frameworks tend to share the common core. All frameworks cover basic topics like risk management, backup, malware, personnel awareness or access management in their respective sections.
Cyberday’s universal cyber security language technology creates you a single security plan and ensures you implement the common parts of frameworks just once. You focus on implementing your plan, we automate the compliance part - for current and upcoming frameworks.
Start your free trial
Get to know Cyberday
Start your free trial
Cyberday is your all-in-one solution for building a secure and compliant organization. Whether you're setting up a cyber security plan, evaluating policies, implementing tasks, or generating automated reports, Cyberday simplifies the entire process.
With AI-driven insights and a user-friendly interface, it's easier than ever to stay ahead of compliance requirements and focus on continuous improvement.
Clear framework compliance plans
Activate relevant frameworks and turn them into actionable policies tailored to your needs.
Credible reports to proof your compliance
Use guided tasks to ensure secure implementations and create professional reports with just a few clicks.
AI-powered improvement suggestions
Focus on the most impactful improvements in your compliance with help from Cyberday AI.
1.1 (MIL2): Manage IT and OT Asset Inventory
C2M2: MIL1
1.1 (MIL3): Manage IT and OT Asset Inventory
C2M2: MIL1
1.1.1: Availability of information security policies
TISAX
1.1.1: Identify the organisation’s strategy and priorities
NSM ICT-SP
1.1.2: Identify the organisation’s structures and processes for security management
NSM ICT-SP
1.1.3: Identify the organisation’s processes for ICT risk management
NSM ICT-SP
1.1.4: Identify the organisation’s tolerances for ICT risk
NSM ICT-SP
1.1.5: Identify the organisation’s deliverables, information systems and supporting ICT functions
NSM ICT-SP
1.1.6: Identify information processing and data flow
NSM ICT-SP
1.2 (MIL2): Manage Information Asset Inventory
C2M2: MIL1
1.2 (MIL3): Manage Information Asset Inventory
C2M2: MIL1
1.2.1: Establish a process to identify devices and software in use at the organisation
NSM ICT-SP
1.2.1: Scope of Information Security management
TISAX
1.2.2: Establish organisational guidelines for approved devices and software
NSM ICT-SP
1.2.2: Information Security Responsibilities
TISAX
1.2.3: Identify devices in use at the organisation
NSM ICT-SP
1.2.3: Information Security requirements in projects
TISAX
1.2.4: Definition of responsibilities with service providers
TISAX
1.2.4: Identify the software in use at the organisation
NSM ICT-SP
1.2: Manage Information Asset Inventory
C2M2: MIL1
1.3 (MIL2): Manage IT and OT Asset Configuration
C2M2: MIL1
1.3 (MIL3): Manage IT and OT Asset Configuration
C2M2: MIL1
1.3.1: Identification of information assets
TISAX
1.3.1: Identify the users of the information systems
NSM ICT-SP
1.3.2: Classification of information assets
TISAX
1.3.2: Identify and define the different user categories
NSM ICT-SP
1.3.3: Identify roles and responsibilities linked especially to ICT security
NSM ICT-SP
1.3.3: Use of approved external IT services
TISAX
1.3.4: Use of approved software
TISAX
1.3: Manage IT and OT Asset Configuration
C2M2: MIL1
1.4 (MIL2): Manage Changes to IT and OT Assets
C2M2: MIL1
1.4 (MIL3): Manage Changes to IT and OT Assets
C2M2: MIL1
1.4.1: Management of Information Security Risks
TISAX
1.4: Manage Changes to IT and OT Assets
C2M2: MIL1
1.5 (MIL1): Management Activities for the ASSET domain
C2M2: MIL1
1.5 (MIL2): Management Activities for the ASSET domain
C2M2: MIL1
1.5 (MIL3): Management Activities for the ASSET domain
C2M2: MIL1
1.5.1: Assessment of policies and requirements
TISAX
1.5.2: External review of ISMS
TISAX
1.5: Management Activities for the ASSET domain
C2M2: MIL1
1.6.1: Reporting of security events
TISAX
1.6.2: Management of reported events
TISAX
1.6.3: Crisis preparedness
TISAX
10 §: Johdon vastuu
KyberTL
10. Processing of personal data relating to criminal convictions and offences
GDPR
10.1 (MIL2): Establish Cybersecurity Program Strategy
C2M2: MIL1
10.1 (MIL3): Establish Cybersecurity Program Strategy
C2M2: MIL1
10.1.1: Policy on the use of cryptographic controls
ISO27 Full
10.1.2: Key management
ISO27 Full
10.1.2: Key management
ISO 27017
10.1: Continuous improvement
ISO27k1 Full
10.1: Cryptographic controls
ISO27 Full
10.1: Cryptographic controls
ISO 27017
10.1: Establish Cybersecurity Program Strategy
C2M2: MIL1
10.2 (MIL2): Establish and Maintain Cybersecurity Program
C2M2: MIL1
10.2 (MIL3): Establish and Maintain Cybersecurity Program
C2M2: MIL1
10.2: Establish and Maintain Cybersecurity Program
C2M2: MIL1
10.2: Non-conformity and corrective action
ISO27k1 Full
10.3 (MIL1): Management Activities for the PROGRAM domain
C2M2: MIL1
10.3 (MIL2): Management Activities for the PROGRAM domain
C2M2: MIL1
10.3 (MIL3): Management Activities for the PROGRAM domain
C2M2: MIL1
10.3: Management Activities for the PROGRAM domain
C2M2: MIL1
10: Cryptography
ISO27 Full
10: Cryptography
ISO 27017
10: Cybersecurity Program Management (PROGRAM)
C2M2: MIL1
10: Prosessi väärinkäytöksiin reagoimiseksi
Sec overview
11 §: Poikkeamailmoitukset viranomaiselle
KyberTL
11. Processing which does not require identification
GDPR
11.1.1: Physical security perimeter
ISO27 Full
11.1.2: Physical entry controls
ISO27 Full
11.1.3: Securing offices, rooms and facilities
ISO27 Full
11.1.4: Protecting against external and environmental threats
ISO27 Full
11.1.5: Working in secure areas
ISO27 Full
11.1.6: Delivery and loading areas
ISO27 Full
11.1: Secure areas
ISO27 Full
11.2.1: Equipment siting and protection
ISO27 Full
11.2.2: Supporting utilities
ISO27 Full
11.2.3: Cabling security
ISO27 Full
11.2.4: Equipment maintenance
ISO27 Full
11.2.5: Removal of assets
ISO27 Full
11.2.6: Security of equipment and assets off-premises
ISO27 Full
11.2.7: Secure disposal or re-use of equipment
ISO27 Full
11.2.7: Secure disposal or re-use of equipment
ISO 27017
11.2.8: Unattended user equipment
ISO27 Full
11.2.9: Clear desk and clear screen policy
ISO27 Full
11.2: Equipment
ISO27 Full
11.2: Equipment
ISO 27017
11: Digiturvan mittarien määrittäminen
Sec overview
11: Physical and environmental security
ISO27 Full
11: Physical and environmental security
ISO 27017
12 §: Luotettavuutta edellyttävien tehtävien tunnistaminen ja luotettavuudesta varmistuminen
TiHL
12 §: Poikkeamaa koskeva väliraportti
KyberTL
12. Transparent information, communication and modalities for the exercise of the rights of the data subject
GDPR
12.1.1: Documented operating procedures
ISO27 Full
12.1.2: Change management
ISO27 Full
12.1.3: Capacity management
ISO27 Full
12.1.4: Separation of development, testing and operational environments
ISO27 Full
12.1: Operational procedures and responsibilities
ISO27 Full
12.2.1: Controls against malware
ISO27 Full
12.2: Protection from malware
ISO27 Full