1.3.4: Use of approved software

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

Objective: Information processing is mostly done using of specific software. Security issues in software will easily become a risk for the information processed. Accordingly, software must be appropriately managed.

Requirements (must): Software is approved before installation or use. The following aspects are considered:
- Limited approval for specific use-cases or roles
- Conformance to the information security requirements
- Software use rights and licensing
- Source / reputation of the software
Software approval also applies to special purpose software such as maintenance tools

Requirements (should): The types of software such as firmware, operating systems, applications, libraries, device drivers to be managed are determined.
Repositories of managed software exist
The software repositories are protected against unauthorized manipulation
Approval of software is regularly reviewed
Software versions and patch levels are known

This requirement is part of the framework:  
TISAX: Information security
Best practices
How to implement:
1.3.4: Use of approved software
This policy on
1.3.4: Use of approved software
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: Information processing is mostly done using of specific software. Security issues in software will easily become a risk for the information processed. Accordingly, software must be appropriately managed.

Requirements (must): Software is approved before installation or use. The following aspects are considered:
- Limited approval for specific use-cases or roles
- Conformance to the information security requirements
- Software use rights and licensing
- Source / reputation of the software
Software approval also applies to special purpose software such as maintenance tools

Requirements (should): The types of software such as firmware, operating systems, applications, libraries, device drivers to be managed are determined.
Repositories of managed software exist
The software repositories are protected against unauthorized manipulation
Approval of software is regularly reviewed
Software versions and patch levels are known

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
1.3.4: Use of approved software
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
1.3.4: Use of approved software
of the framework  
TISAX: Information security
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Approval process before deploying new software
Critical
High
Normal
Low
3
requirements
System management
Data system management

Approval process before deploying new software

This task helps you comply with the following requirements

Management process for approved software
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.