5.2.6: IT System Management

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

Objective: The objective of technical checks is the detection of states which can jeopardize the availability, confidentiality or integrity of IT systems and services.

Requirements (must): Requirements for auditing IT systems or services are determined.
The scope of the system audit is specified in a timely manner.
System or service audits are coordinated with the operator and users of the IT systems or services.
The results of system or service audits are stored in a traceable manner and reported to the relevant management.
Measures are derived from the results.

Requirements (should): System and service audits are planned taking into account any security risks they might cause (e.g. disturbances).
Regular system or service audits are performed
- carried out by qualified personnel
- suitable tools (e.g. vulnerability scanners) are used for system and service audits (if applicable)
- performed from the internet and the internal network
Within a reasonable period following completion of the audit, a report is prepared.

This requirement is part of the framework:  
TISAX: Information security

Other requirements of the framework

28755
5.2.6: IT System Management
Best practices
How to implement:
5.2.6: IT System Management
This policy on
5.2.6: IT System Management
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

Objective: The objective of technical checks is the detection of states which can jeopardize the availability, confidentiality or integrity of IT systems and services.

Requirements (must): Requirements for auditing IT systems or services are determined.
The scope of the system audit is specified in a timely manner.
System or service audits are coordinated with the operator and users of the IT systems or services.
The results of system or service audits are stored in a traceable manner and reported to the relevant management.
Measures are derived from the results.

Requirements (should): System and service audits are planned taking into account any security risks they might cause (e.g. disturbances).
Regular system or service audits are performed
- carried out by qualified personnel
- suitable tools (e.g. vulnerability scanners) are used for system and service audits (if applicable)
- performed from the internet and the internal network
Within a reasonable period following completion of the audit, a report is prepared.

Read below what concrete actions you can take to improve this ->
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
5.2.6: IT System Management
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

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
5.2.6: IT System Management
of the framework  
TISAX: Information security
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Defining IT system auditing requirements
Critical
High
Normal
Low
3
requirements
System management
Data system management

Defining IT system auditing requirements

This task helps you comply with the following requirements

Protection of data systems during audit-related testing
Critical
High
Normal
Low
2
requirements
System management
Data system management

Protection of data systems during audit-related testing

This task helps you comply with the following requirements

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

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.