Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Objective: Security zones provide physical protection of information assets. The more sensitive the information assets to be processed are the more protective measures are required.
Requirements (must): A security zone concept including the associated protective measures based on the requirements for the handling of information assets is in place:
- Physical conditions (e.g. premises / buildings / spaces) are considered in the definition of security zones,
- This also includes delivery and shipping areas.
The defined protective measures are implemented.
The code of conduct for security zones is known to all persons involved.
Requirements (should): Procedures for allocation and revocation of access rights are established.
Visitor management policies (including registration and escorting of visitors) are defined.
Policies for carrying along and using mobile IT devices and mobile data storage devices (e.g. registration before they are carried along, identification obligations) are defined and implemented.
Network/infrastructure components (own or customer networks) are protected against unauthorized access.
External properties used for storing and processing information assets are considered in the security zone concept (e.g. storage rooms, garages, workshops, test tracks, data processing centres).
Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Objective: Security zones provide physical protection of information assets. The more sensitive the information assets to be processed are the more protective measures are required.
Requirements (must): A security zone concept including the associated protective measures based on the requirements for the handling of information assets is in place:
- Physical conditions (e.g. premises / buildings / spaces) are considered in the definition of security zones,
- This also includes delivery and shipping areas.
The defined protective measures are implemented.
The code of conduct for security zones is known to all persons involved.
Requirements (should): Procedures for allocation and revocation of access rights are established.
Visitor management policies (including registration and escorting of visitors) are defined.
Policies for carrying along and using mobile IT devices and mobile data storage devices (e.g. registration before they are carried along, identification obligations) are defined and implemented.
Network/infrastructure components (own or customer networks) are protected against unauthorized access.
External properties used for storing and processing information assets are considered in the security zone concept (e.g. storage rooms, garages, workshops, test tracks, data processing centres).
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.
In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.
When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.
Sets the overall compliance standard or regulation your organization needs to follow.
.svg)
.svg)
.svg)
Break down the framework into specific obligations that must be met.
.svg)
Concrete actions and activities your team carries out to satisfy each requirement.
Documented rules and practices that are created and maintained as a result of completing tasks.
