8.28: Veilig coderen

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

Bij het maken van software moeten principes voor veilig coderen worden gevolgd. Dit zorgt ervoor dat software op een veilige manier wordt geschreven. Het vermindert de kans op potentiële kwetsbaarheden die de informatiebeveiliging in gevaar kunnen brengen. Deze procedures moeten worden uitgebreid tot softwarecomponenten van derden en open-sourcesoftware. De organisatie moet veilige coderingspraktijken implementeren die kunnen omgaan met het snel veranderende dreigingslandschap.

Best practices
How to implement:
8.28: Veilig coderen
This policy on
8.28: Veilig coderen
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.

Bij het maken van software moeten principes voor veilig coderen worden gevolgd. Dit zorgt ervoor dat software op een veilige manier wordt geschreven. Het vermindert de kans op potentiële kwetsbaarheden die de informatiebeveiliging in gevaar kunnen brengen. Deze procedures moeten worden uitgebreid tot softwarecomponenten van derden en open-sourcesoftware. De organisatie moet veilige coderingspraktijken implementeren die kunnen omgaan met het snel veranderende dreigingslandschap.

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.28: Veilig coderen
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.28: Veilig coderen
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
Separation of production, testing and development environments
Critical
High
Normal
Low
Regular vulnerability scanning
Critical
High
Normal
Low
Process for monitoring and tracking outsourced development work
Critical
High
Normal
Low
33
requirements
Development and cloud
Secure development

Process for monitoring and tracking outsourced development work

This task helps you comply with the following requirements

General rules for reviewing and publishing code
Critical
High
Normal
Low
Vulnerability monitoring in used third-party or open source libraries
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.