SOC 2 (Systems and Organization Controls)
Requirement

CC2.3: Communication with external parties

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

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

Fulfill this requirement by completing the tasks below ->
SOC 2 (Systems and Organization Controls)
CC2.3: Communication with external parties
This requirement is part of the framework:  
SOC 2 (Systems and Organization Controls)

Other requirements of the framework

20197
CC2.2: Internal communication of information
20196
CC2.1: Quality information to support internal controls
20198
CC2.3: Communication with external parties
20200
CC3.1: Sufficient specifying of objectives
20201
CC3.2: Identification of risks related to objectives
Best practices
How to implement:
CC2.3: Communication with external parties

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

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

Read below what concrete actions you can take to improve this ->
CC2.3: Communication with external parties
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to
CC2.3: Communication with external parties
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
31 requirements
No other tasks found.
Complete these tasks in Cyberday ISMS ->

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
CC2.3: Communication with external parties
of the framework  
SOC 2 (Systems and Organization Controls)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
31 requirements
Information security policy -report publishing, informing and maintenance
Critical
High
Normal
Low
39
requirements
Risk management and leadership
Cyber security management

Information security policy -report publishing, informing and maintenance

This task helps you comply with the following requirements

Članak 29.a: UpravljanjeNIS2 Croatia
10 §: Johdon vastuuKyberturvallisuuslaki
9.2 §: Kyberturvallisuuden toimintaperiaatteetKyberturvallisuuslaki
1.1.1: Availability of information security policiesTISAX
31 § 1°: Approbation des mesures de gestion des risques de cybersécuritéNIS2 Belgium
30 § 5°: Analyse des risques et politique de sécurité de l'informationNIS2 Belgium
1.1.2: Identify the organisation’s structures and processes for security managementNSM ICT-SP
PR.AT-4: Senior executives understand their roles and responsibilities.CyberFundamentals
ID.GV-1: Organizational cybersecurity policy is established and communicated.CyberFundamentals
14.5.1): Kibernetinio saugumo politika ir rizikos analizėsNIS2 Lithuania
Data processing partner listing and owner assignment
Critical
High
Normal
Low
44
requirements
Partner management
Agreements and monitoring

Data processing partner listing and owner assignment

This task helps you comply with the following requirements

Članak 30.1.d: Sigurnost lanca opskrbeNIS2 Croatia
9.4 §: Toimitusketjun hallinta ja valvontaKyberturvallisuuslaki
1.2.4: Definition of responsibilities with service providersTISAX
1.3.3: Use of approved external IT servicesTISAX
6.1.1: Partner Information securityTISAX
9.5.1: Management of data transferTISAX
30 § 3.4°: La sécurité de la chaîne d'approvisionnementNIS2 Belgium
30 § 4°: Définir et contrôler les mesures de sécurité requises pour la chaîne d'approvisionnementNIS2 Belgium
ID.SC-3: Contracts with suppliers and third-party partners are used to implement appropriate measures designed to meet the objectives of an organization’s cybersecurity program and Cyber Supply Chain Risk Management Plan.CyberFundamentals
ID.SC-2: Suppliers and third-party partners of information systems, components, and services are identified, prioritized, and assessed using a cyber supply chain risk assessment process.CyberFundamentals
Communication plan for information security management system
Critical
High
Normal
Low
16
requirements
Risk management and leadership
Cyber security management

Communication plan for information security management system

This task helps you comply with the following requirements

Članak 29.a: UpravljanjeNIS2 Croatia
31 § 1°: Approbation des mesures de gestion des risques de cybersécuritéNIS2 Belgium
2.10.1: Include security in the organisation’s change management processNSM ICT-SP
RC.CO-2: Reputation is repaired after an incident.CyberFundamentals
ID.GV-1: Organizational cybersecurity policy is established and communicated.CyberFundamentals
14.5.2): Aukščiausiosios vadovybės atsakomybėNIS2 Lithuania
Article 14: CommunicationDORA
RC.CO-2: ReputationNIST
20.1: Top management commitmentNIS2
CC2.3: Communication with external partiesSOC 2
Documentation of other stakeholders
Critical
High
Normal
Low
19
requirements
Partner management
Agreements and monitoring

Documentation of other stakeholders

This task helps you comply with the following requirements

Članak 30.1.d: Sigurnost lanca opskrbeNIS2 Croatia
9.4 §: Toimitusketjun hallinta ja valvontaKyberturvallisuuslaki
1.3.3: Use of approved external IT servicesTISAX
30 § 3.4°: La sécurité de la chaîne d'approvisionnementNIS2 Belgium
ID.SC-1: Cyber supply chain risk management processes are identified, established, assessed, managed, and agreed to by organizational stakeholders.CyberFundamentals
14.5.5): Tiekimo grandinės saugumąNIS2 Lithuania
GV.OC-02: Stakeholders' needs in cybersecurity risk managementNIST 2.0
15.1: Establish and Maintain an Inventory of Service ProvidersCIS 18
27.(c): Piegādes ķēdes drošībaNIS2 Latvia
3: Keskeisten sidos- ja asiakasryhmien kartoitusDigiturvan kokonaiskuvapalvelu
Keeping contact with relevant authorities
Critical
High
Normal
Low
18
requirements
Partner management
Agreements and monitoring

Keeping contact with relevant authorities

This task helps you comply with the following requirements

Članak 37: Obavještavanje o značajnim incidentimaNIS2 Croatia
11 §: Poikkeamailmoitukset viranomaiselleKyberturvallisuuslaki
1.2.2: Information Security ResponsibilitiesTISAX
34 § 1°: Notifications d'incidents au CSIRT et aux bénéficiaires des servicesNIS2 Belgium
RC.CO-1: Public relations are managed.CyberFundamentals
18.1.: Pranešimai apie incidentus CSIRT ir paslaugų gavėjamsNIS2 Lithuania
RC.CO-1: Public relationsNIST
GV.RR-02: Roles and responsibilities in cybersecurity risk managementNIST 2.0
17.2: Establish and Maintain Contact Information for Reporting Security IncidentsCIS 18
34.(1): Incidentu novēršana un informēšanaNIS2 Latvia
Communication to stakeholders on continuity plans
Critical
High
Normal
Low
18
requirements
Risk management and leadership
Continuity management

Communication to stakeholders on continuity plans

This task helps you comply with the following requirements

Članak 30.1.c: Kontinuitet poslovanjaNIS2 Croatia
9.10 §: Varmuuskopiointi ja jatkuvuuden hallintaKyberturvallisuuslaki
30 § 3.3°: La continuité et la gestion des crisesNIS2 Belgium
RC.CO-2: Reputation is repaired after an incident.CyberFundamentals
14.5.4): Veiklos tęstinumąNIS2 Lithuania
Article 11: Response and recoveryDORA
RS.CO-03: Sharing Information with stakeholdersNIST 2.0
ID.IM-04: Incident response and cybersecurity plansNIST 2.0
28.(1): Kiberriska pārvaldības un nepārtrauktības plāniNIS2 Latvia
Article 39: Components of the ICT business continuity planDORA simplified RMF
Contact with industry-specific interest groups
Critical
High
Normal
Low
12
requirements
Partner management
Agreements and monitoring

Contact with industry-specific interest groups

This task helps you comply with the following requirements

6.1.4: Contact with special interest groupsISO 27001
ID.RA-2: Cyber threat intelligenceNIST
RS.CO-5: Voluntary information sharingNIST
RC.CO-1: Public relationsNIST
14.5.13): Kitus taikomus kibernetinio saugumo reikalavimusNIS2 Lithuania
5.6: Contact with special interest groupsISO 27001
CC2.3: Communication with external partiesSOC 2
RS.CO-5: Voluntary information sharing occurs with external stakeholders to achieve broader cybersecurity situational awareness.CyberFundamentals
RC.CO-1: Public relations are managed.CyberFundamentals
ID.RA-2: Cyber threat intelligence is received from information sharing forums and sources.CyberFundamentals
Complete these tasks in Cyberday ISMS ->

The ISMS component hierachy

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way‍
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.
Start free trial
Effortless compliance improvement
Widest framework library in EU
Extensive support

Start your compliance journey

Use in MS Teams or use your browser with Slack integration.
Risk free trial. No credit card required. Stop at any time.

Start free 14-day trial
Book a meeting
How it works?
SummarySecurity tasks and assuranceDocumentation workflowsEmployee guidelinesReporting templates
Use cases
By frameworkAll frameworksISO 27001NIS2 directiveNIST CSFCSA CCMISO 27701GDPRISO 27017ISO 27018
By methodCyber risk managementEmployee awarenessCompliance reportingControl managementAsset managementPrivacy managementVendor assessments
Resources
AcademyWebinarsBlogHelp articlesVideo coursesContent libraryGuidesNewsletterLeave a reviewPartner programTeamTerms of usePrivacy policy
Contact us
+358 10 231 6010
team@cyberday.ai
App works in:
Known in Finland as Digiturvamalli
© Cyberday Inc. Kalevantie 2 33100 Tampere, Finland
Cyberday.ai - Improve and certify your cyber security