§ 3.1.13: Skydd mot skadlig kod

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

Myndigheten ska, vid utveckling, anskaffning eller utkontraktering av informationssystem, identifiera krav på säkerhet avseende skydd mot skadlig kod.

Myndigheten ska dokumentera vilka säkerhetsåtgärder som valts för att möta respektive krav.

This requirement is part of the framework:  
MSBFS 2020:7 (Sverige)
Best practices
How to implement:
§ 3.1.13: Skydd mot skadlig kod
This policy on
§ 3.1.13: Skydd mot skadlig kod
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.

Myndigheten ska, vid utveckling, anskaffning eller utkontraktering av informationssystem, identifiera krav på säkerhet avseende skydd mot skadlig kod.

Myndigheten ska dokumentera vilka säkerhetsåtgärder som valts för att möta respektive krav.

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
§ 3.1.13: Skydd mot skadlig kod
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
§ 3.1.13: Skydd mot skadlig kod
of the framework  
MSBFS 2020:7 (Sverige)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Selection and use of malware detection software on all devices
Critical
High
Normal
Low
Defining requirements for malware protection
Critical
High
Normal
Low
Automatically updating and running malware prevention software
Critical
High
Normal
Low
Regular malware inspection of data systems supporting critical business processes
Critical
High
Normal
Low
44
requirements
Technical cyber security
Malware protection

Regular malware inspection of data systems supporting critical business processes

This task helps you comply with the following requirements

Procedures and data sources for gathering reliable information about malware
Critical
High
Normal
Low
Training the use of security systems and reporting of malware attacks
Critical
High
Normal
Low
7
requirements
Personnel security
Cyber security training

Training the use of security systems and reporting of malware attacks

This task helps you comply with the following requirements

Automatic blocking and detecting of unauthorized software
Critical
High
Normal
Low
20
requirements
Technical cyber security
Malware protection

Automatic blocking and detecting of unauthorized software

This task helps you comply with the following requirements

Instructing and training staff regarding malware
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.