richardk/iso27diy-corp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Cleaning up the Sparks folder

Browse source
This commit is contained in:
Richard Kranendonk 2026-05-18 09:31:41 +02:00
parent eb610a79b6
commit 96cd8fea7b
78 changed files with 149 additions and 181 deletions
Download patch file Download diff file Expand all files Collapse all files

14
Corpus/Sparks/ISMS/Ideas about enforcement.md Normal file
View file

@ -0,0 +1,14 @@
# Ideas about enforcement
The coverage of [[Enforcement tooling]] will not be complete, if only because their implementation will always be one step behind organizational reality. There will be information assets out of scope, by choice or accident.
There will be situations where the improper handling of assets is not prevented by such tooling, and employees would need to be aware of, or deduce from content, the classification of those assets, and make an informed decission on the proper handling.
The underlying idea is that I personally prefer that people have freedom of choice and be supported in making informed decissions.
that is not only morally preferable, but it's a necessigty precisely because there will always be situations in which they *need* to decide for themselves.
There's also a link here to different stakeholders with different interests. Think of your stereotypical IT Guy, who wants to screw everything down, and Marketing Guy, who wants maximum freedom in the data lake.
Related:
- [Labeling of information in the digital domain](Labeling%20of%20information%20in%20the%20digital%20domain.md).
- [Stakeholder Analysis](../Stakeholder%20Analysis.md)