Content library
SOC 2 (Systems and Organization Controls)
CC2.3: Communication with external parties

Requirement description

COSO Principle 15: The entity communicates with external parties regarding matters affecting the functioning of internal control.

Points of focus:

- Communicates to External Parties
- Enables Inbound Communications
- Communicates With the Board of Directors
- Provides Separate Communication Lines
- Selects Relevant Method of Communication
- Communicates Objectives Related to Confidentiality and Changes to Objectives
- Communicates Objectives Related to Privacy and Changes to Objectives
- Communicates Information About System Operation and Boundaries
- Communicates System Objectives
- Communicates System Responsibilities
- Communicates Information on Reporting System Failures, Incidents, Concerns, and Other Matters

How to fill the requirement

SOC 2 (Systems and Organization Controls)

CC2.3: Communication with external parties

Task name
Priority
Status
Theme
Policy
Other requirements
Data processing partner listing and owner assignment
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Partner management
Agreements and monitoring
41
requirements

Examples of other requirements this task affects

26. Joint controllers
GDPR
28. Data processor
GDPR
44. General principle for transfers
GDPR
8.1.1: Inventory of assets
ISO27 Full
13.2.2: Agreements on information transfer
ISO27 Full
See all related requirements and other information from tasks own page.
Go to >
Data processing partner listing and owner assignment
1. Task description

The organization must maintain a list of partners who have access to confidential information. System vendors and processors of personal data are listed separately from other stakeholders because they play an active role in the processing of data.

Information security policy -report publishing, informing and maintenance
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Cyber security management
37
requirements

Examples of other requirements this task affects

5: Information security policies
ISO27 Full
5.1: Management direction for information security
ISO27 Full
5.1.1: Policies for information security
ISO27 Full
5.1.2: Review of the policies for information security
ISO27 Full
T01: Turvallisuusperiaatteet
Katakri
See all related requirements and other information from tasks own page.
Go to >
Information security policy -report publishing, informing and maintenance
1. Task description

The organization has an information security policy developed and approved by top management. The policy shall include at least the following:

  • the basis for setting the organization’s security objectives
  • commitment to meeting information security requirements
  • commitment to continuous improvement of the information security management system

In addition, the task owner shall ensure that:

  • the is appropriate for the organization's business idea
  • the policy is communicated to the entire organization
  • the policy is available to stakeholders as appropriate
Keeping contact with relevant authorities
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Partner management
Agreements and monitoring
14
requirements

Examples of other requirements this task affects

6.1.3: Contact with authorities
ISO27 Full
RC.CO-1: Public relations
NIST
5.5: Contact with authorities
ISO27k1 Full
23.1: Incident notifications to CSIRT and recipients of services
NIS2
CC2.3: Communication with external parties
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Keeping contact with relevant authorities
1. Task description

The organization lists the relevant government actors with whom it is important to actively contact and, if necessary, get in touch quickly. These authorities include national law enforcement and supervisory authorities.

A clear contact person should be defined for the relevant authorities to act as a contact point for the organization.

Documentation of other stakeholders
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Partner management
Agreements and monitoring
16
requirements

Examples of other requirements this task affects

HAL-04.6: Suojattavat kohteet - sidosryhmät
Julkri
HAL-05: Vaatimukset
Julkri
4.2: Interested parties
ISO27k1 Full
3: Keskeisten sidos- ja asiakasryhmien kartoitus
Sec overview
21.2.d: Supply chain security
NIS2
See all related requirements and other information from tasks own page.
Go to >
Documentation of other stakeholders
1. Task description

The organization shall identify

  • the stakeholders relevant to the security management system
  • the security requirements set by these stakeholders

Data system providers and personal data processors are treated through separate tasks.

Communication plan for information security management system
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Cyber security management
13
requirements

Examples of other requirements this task affects

RC.CO-2: Reputation
NIST
5.1: Leadership and commitment
ISO27k1 Full
7.4: Communication
ISO27k1 Full
20.1: Top management commitment
NIS2
CC2.2: Internal communication of information
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Communication plan for information security management system
1. Task description

The organization shall determine which issues related to the information security management system need to be communicated on a regular basis. The plan must include the answers, e.g. to the following points:

  • What issues are communicated? These can be e.g. new or changed security objectives
  • How and when to communicate?What channels are used and how often?
  • To whom is communicated? How often for security executives, how often for the entire organization or partners.
  • Who takes part? Who has the right to message and from whom, for example, messages should be approved.

Task owner will take care of the implementation of the plan and regular evaluation of its effectiveness.

Contact with industry-specific interest groups
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Partner management
Agreements and monitoring
12
requirements

Examples of other requirements this task affects

6.1.4: Contact with special interest groups
ISO27 Full
ID.RA-2: Cyber threat intelligence
NIST
RS.CO-5: Voluntary information sharing
NIST
RC.CO-1: Public relations
NIST
5.6: Contact with special interest groups
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Contact with industry-specific interest groups
1. Task description

The organization shall actively maintain contacts with stakeholders relevant to the organization's operations and other relevant actors related to the organization's operations and security.

The goal is especially to:

  • increase knowledge of best practices and keep up to date with relevant security information
  • ensure that organisation's understanding of the security environment is up-to-date and complete
Communication to stakeholders on continuity plans
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
14
requirements

Examples of other requirements this task affects

VAR-03: Jatkuvuussuunnitelmat
Julkri
34: Sidosryhmien välisen viestinnän mahdollistaminen
Sec overview
21.2.c: Business continuity and backups
NIS2
CC2.3: Communication with external parties
SOC 2
CC7.5: Recovery from security incidents
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Communication to stakeholders on continuity plans
1. Task description

The organization shall have procedures in place to communicate effectively with stakeholders and other participants during continuity plans and survival procedures.

Communication plans related to continuity plans shall include:

  • Responsible persons, related stakeholders and other necessary contact information
  • Clear criteria for the situation where continuity communication will be implemented
  • A clear description of the staff implementing the continuity communication in each situation and the recipients to whom the communication will be sent
  • References to the templates and tools to be used

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