Skip to content

The Architectural Security Patterns library of the Belgian Cyber Security Coalition

Notifications You must be signed in to change notification settings

CSC-ESA/Patterns

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

43 Commits
 
 
 
 
 
 
 
 

Repository files navigation

CSC-Patterns

This is the homepage for the Architectural Security Patterns library of the Belgian Cyber Security Coalition.

To go to the Patterns Library environment, click here

Viewpoints

Threat viewpoint Control viewpoint
Concerns Understand what is being built and what can go wrong. Optionally this viewpoint shows the controls that can counter the threats Understand what we are going to do about it and which elements in the architecture realize the necessary controls
Abstraction level Logical Logical
Layers All layers All layers
Aspects Active structure Active structure
Allowed elements * Business event (threat event)
* Application component
* Node
* Communication network
* Requirement
* Triggering relationship
* Association relationship
* Influencing relationship
* Specialization relationship
* Business event (threat event)
* Application component
* Node
* Communication network
* Requirement
* Triggering relationship
* Specialization relationship
Modeling conventions * We use triggering relationships between active structure to model interaction
* We use nesting between active elements and communication networks (zones)
* We use directed association relationships to link controls to threats (from control to threat)
* We use directed association relationships to link an element to a threat (from element to threat)
* Each triggering relationship must have a property 'Protocol' and its value must be completed.
* We use specialization relationships to link detailed requirements to high-level requirements.
* We use triggering relationships between active structure to model interaction
* We use nesting between active elements and communication networks (zones)
* We use realization relationships between active structures and requirements to model which structure realizes a certain requirement
* We use specialization relationships to link detailed requirements to high-level requirements.
* Each triggering relationship must have two properties: 'Protocol' and 'Authentication', and the values must be completed.
* Each triggering relationship must have the label expression: [${property:Protocol}][${property:Authentication}]

Methodology

Contributing

References

  1. Open Security Architecture
  2. securitypatterns.io

About

The Architectural Security Patterns library of the Belgian Cyber Security Coalition

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •