8.34: Bescherming van informatiesystemen tijdens audits

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

Het is noodzakelijk om activiteiten tussen testers en het juiste management te plannen en af te stemmen om de impact van audits en andere assurance-activiteiten op operationele systemen en bedrijfsprocessen te minimaliseren. Richtlijnen hiervoor zijn onder meer het beperken van de reikwijdte van technische tests en het beperken van tests tot alleen-lezen toegang waar mogelijk. Audittests die de beschikbaarheid van het systeem kunnen beïnvloeden, moeten buiten kantooruren worden gepland. Alle toegang moet worden gecontroleerd en geregistreerd voor auditdoeleinden.

This requirement is part of the framework:  
NEN 7510 - Informatiebeveiliging in de zorg (Nederlands)

Other requirements of the framework

47202
8.34: Bescherming van informatiesystemen tijdens audits
Best practices
How to implement:
8.34: Bescherming van informatiesystemen tijdens audits
This policy on
8.34: Bescherming van informatiesystemen tijdens audits
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.

Het is noodzakelijk om activiteiten tussen testers en het juiste management te plannen en af te stemmen om de impact van audits en andere assurance-activiteiten op operationele systemen en bedrijfsprocessen te minimaliseren. Richtlijnen hiervoor zijn onder meer het beperken van de reikwijdte van technische tests en het beperken van tests tot alleen-lezen toegang waar mogelijk. Audittests die de beschikbaarheid van het systeem kunnen beïnvloeden, moeten buiten kantooruren worden gepland. Alle toegang moet worden gecontroleerd en geregistreerd voor auditdoeleinden.

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
8.34: Bescherming van informatiesystemen tijdens audits
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
8.34: Bescherming van informatiesystemen tijdens audits
of the framework  
NEN 7510 - Informatiebeveiliging in de zorg (Nederlands)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Protection of data systems during audit-related testing
Critical
High
Normal
Low
3
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.