Content library
ISO 27001 (2022): Full
5.23: Information security for use of cloud services

Requirement description

Organization needs to establish processes for acquiring, using, managing, and exiting from cloud services that align with the organization's information security requirements. Clearly defining and managing information security aspects when utilizing cloud services is essential. It can be either integrated into the current approach for managing services offered by external parties, or created as a more separate own policy.

How to fill the requirement

ISO 27001 (2022): Full

5.23: Information security for use of cloud services

Task name
Priority
Status
Theme
Policy
Other requirements
General principles regarding the use of cloud services
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
System management
Data system management
1
requirements

Examples of other requirements this task affects

5.23: Information security for use of cloud services
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
General principles regarding the use of cloud services
1. Task description

Organization must define (in addition to more detailed practices regarding supplier responsibilities, incidents and the procurement of cloud services) the general principles for managing information security risks related to the use of cloud services.

Principles must take into account e.g.:

  • how to utilize security features made possible by service providers
  • how to demand evidence of security measures implemented by service providers
  • what factors must be taken into account in own operations when utilizing a large number service providers
  • considering use of cloud services in own information security risk management process
  • procedures for ending the use of cloud services
General rules for the procurement of data systems
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
System management
Data system procurement
15
requirements

Examples of other requirements this task affects

14.1.1: Information security requirements analysis and specification
ISO27 Full
13 §: Tietoaineistojen ja tietojärjestelmien tietoturvallisuus
TiHL
HAL-16: Hankintojen turvallisuus
Julkri
5.23: Information security for use of cloud services
ISO27k1 Full
52: Tietoturva- ja tietousojavaatimukset hankintavaatimuksissa
Sec overview
See all related requirements and other information from tasks own page.
Go to >
General rules for the procurement of data systems
1. Task description

Whenever new data systems are acquired, a pre-defined procurement process and rules are followed. The rules ensure that the supplier is able to guarantee an adequate level of security, taking into account the priority of the system.

Comprehensiveness of contractual terms for cloud service provisioning
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
System management
Data system procurement
5
requirements

Examples of other requirements this task affects

5.23: Information security for use of cloud services
ISO27k1 Full
21.2.e: Secure system acquisition and development
NIS2
See all related requirements and other information from tasks own page.
Go to >
Comprehensiveness of contractual terms for cloud service provisioning
1. Task description

Agreement between a cloud service provider and the organization must include requirements for protecting the organization's data and the availability of services, e.g. in the following ways:

  • providing a solution based on generally accepted architecture and infrastructure standards in the industry
  • managing access rights to meet organizational requirements
  • implementing malware control and protection solutions
  • processing and storage of the organization's sensitive data in approved locations (e.g. a certain country or legislative area)
  • providing support in the event of a data security breach
  • ensuring that the organization's data security requirements are met also in subcontracting chains
  • li>providing support in the collection of digital evidence
  • providing sufficient support when the organization wants to terminate the use of the service
  • required backup and secure management of backups, where applicable
  • information owned by the organization (possibly, e.g. source code, data filled/created for the service) restored upon request or when the service ends
  • notification requirement in relation to significant changes (such as infrastructure, important features, information location or use by subcontractors)
Documenting security-related responsibilities for offered cloud services and utilized data systems
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Development and cloud
Cloud service management
8
requirements

Examples of other requirements this task affects

6: Organization of information security
ISO 27017
CLD 6.3: Relationship between cloud service customer and cloud service provider
ISO 27017
CLD 6.3.1: Shared roles and responsibilities within a cloud computing environment
ISO 27017
6.1: Internal organization
ISO 27017
6.1.3: Contact with authorities
ISO 27017
See all related requirements and other information from tasks own page.
Go to >
Documenting security-related responsibilities for offered cloud services and utilized data systems
1. Task description

When utilizing or offering cloud services, both service provider and customer can have security responsibilities. Service provider may be responsible for technical cyber security but e.g. customer for access management and providing user guidelines for secure usage.

Responsibilities for shared information security roles towards offered cloud services and utilizing cloud-based data systems must be clearly defined and documented by both the cloud service customer and provider.

Process for detecting and reporting security breaches related to the supply chain
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Data breach management
15
requirements

Examples of other requirements this task affects

DE.CM-6: External service provider activity monitoring
NIST
A.10.1: Notification of a data breach involving PII
ISO 27018
5.23: Information security for use of cloud services
ISO27k1 Full
21.2.b (incidents): Incident management
NIS2
P6.3: Record of unauthorized disclosures of personal information
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Process for detecting and reporting security breaches related to the supply chain
1. Task description

The organization shall define the procedures for reporting security breaches in the supply chain. The process must take into account all kinds of roles in the supply chain, whether we are the customer of the end product or one supplier in the chain.

Policies shall take into account agreements with partners and customers and their commitments regarding the reporting obligations of both parties.

Confirming information security roles and responsibilities related to utilized cloud services
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Partner management
Supplier security
12
requirements

Examples of other requirements this task affects

15: Supplier relationships
ISO 27017
15.1: Information security in supplier relationships
ISO 27017
15.1.2: Addressing security within supplier agreements
ISO 27017
15.1.3: Information and communication technology supply chain
ISO 27017
5.23: Information security for use of cloud services
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Confirming information security roles and responsibilities related to utilized cloud services
1. Task description

When an organisation is using a cloud-based data system, the organisation should understand and confirm the related information security roles and responsibilities as stated in the service agreement.

These can include responsibilities related e.g. to:

  • Malware protection
  • Cryptographic controls
  • Backup
  • Vulnerability and incident management
  • Compliance and security testing
  • Authentication, identity and access management

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