5.2.3: Malware protection

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

Objective: The aim is to both technically and organizationally ensure the protection of IT systems against malware.

Requirements (must): Requirements for protection against malware are determined.
Technical and organizational measures for protection against malware are defined and implemented.

Requirements (should): Unnecessary network services are disabled.
Access to network services is restricted to necessary access by means of suitable protective measures (see examples).
Malware protection software is installed and updated automatically at regular intervals (e.g. virus scanner).
Received files and software are automatically inspected for malware prior to their execution (on-access scan).
The entire data contents of all systems is regularly inspected for malware.
Data transferred by central gateways (e.g. e-mail, internet, third-party networks) is automatically inspected by means of protection software:
- Encrypted connections are considered.
Measures to prevent protection software from being deactivated or altered by users are defined and implemented.
Case-related staff awareness measures.
For IT systems operated without the use of malware protection software, alternative measures (e.g. special resilience measures, few services, no active users, network isolation) are implemented.

This requirement is part of the framework:  
TISAX: Information security
Best practices
How to implement:
5.2.3: Malware protection
This policy on
5.2.3: Malware protection
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 aim is to both technically and organizationally ensure the protection of IT systems against malware.

Requirements (must): Requirements for protection against malware are determined.
Technical and organizational measures for protection against malware are defined and implemented.

Requirements (should): Unnecessary network services are disabled.
Access to network services is restricted to necessary access by means of suitable protective measures (see examples).
Malware protection software is installed and updated automatically at regular intervals (e.g. virus scanner).
Received files and software are automatically inspected for malware prior to their execution (on-access scan).
The entire data contents of all systems is regularly inspected for malware.
Data transferred by central gateways (e.g. e-mail, internet, third-party networks) is automatically inspected by means of protection software:
- Encrypted connections are considered.
Measures to prevent protection software from being deactivated or altered by users are defined and implemented.
Case-related staff awareness measures.
For IT systems operated without the use of malware protection software, alternative measures (e.g. special resilience measures, few services, no active users, network isolation) are implemented.

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.3: Malware protection
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.3: Malware protection
of the framework  
TISAX: Information security
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Defining requirements for malware protection
Critical
High
Normal
Low
3
requirements
Technical cyber security
Malware protection

Defining requirements for malware protection

This task helps you comply with the following requirements

Network areas and structurally secure network design
Critical
High
Normal
Low
Defined security arrangements for providing critical network equipment
Critical
High
Normal
Low
Automatic blocking and detecting of unauthorized software
Critical
High
Normal
Low
17
requirements
Technical cyber security
Malware protection

Automatic blocking and detecting of unauthorized software

This task helps you comply with the following requirements

Monitoring the use of the network and information systems to identify anomalies
Critical
High
Normal
Low

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.