diff --git a/Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business drivers.md b/Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business drivers.md index b1c3113..1c4ac4d 100644 --- a/Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business drivers.md +++ b/Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business drivers.md @@ -1,3 +1,3 @@ -- [Perverse prikkels in de normindustrie](../../../../../Marketing/content/Scratch%20file/Perverse%20prikkels%20in%20de%20normindustrie.md) -- [GRC software is geschreven voor domeindeskundigen](../../../../../Marketing/content/Scratch%20file/GRC%20software%20is%20geschreven%20voor%20domeindeskundigen.md) +- [Perverse prikkels in de normindustrie](../../../../../Marketing/publications/Scratch%20file/Perverse%20prikkels%20in%20de%20normindustrie.md) +- [GRC software is geschreven voor domeindeskundigen](../../../../../Marketing/publications/Scratch%20file/GRC%20software%20is%20geschreven%20voor%20domeindeskundigen.md) - [Problems solved 1](../../../../Sparks/Problems%20solved%201.md) diff --git a/Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business model.md b/Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business model.md index 9816b93..50b7ddb 100644 --- a/Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business model.md +++ b/Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business model.md @@ -1,6 +1,6 @@ Child notes: - [Blurbs](../../../../Sparks/Blurbs.md) -- [Toegevoegde waarde van ISO27DIY](../../../../../Marketing/content/Scratch%20file/Toegevoegde%20waarde%20van%20ISO27DIY.md) +- [Toegevoegde waarde van ISO27DIY](../../../../../Marketing/publications/Scratch%20file/Toegevoegde%20waarde%20van%20ISO27DIY.md) - [Friendly targets](../../../../../../πŸ’‘Permanent%20ideas/Friendly%20targets.md) - [Possible Colabs](../../../../../AuditGlue/Possible%20Colabs.md) - [List of possible partners](../../../../../AuditGlue/List%20of%20possible%20partners.md) diff --git a/Corpus/Standards/other/Privacy frameworks list.md b/Corpus/Standards/other/Privacy frameworks list.md index 04d35be..710b044 100644 --- a/Corpus/Standards/other/Privacy frameworks list.md +++ b/Corpus/Standards/other/Privacy frameworks list.md @@ -5,6 +5,6 @@ [Privacy in ISO 27k](../ISO27x/Privacy%20in%20ISO%2027k.md) Related: -- [Privacy protection in Databases](../../../Marketing/content/Scratch%20file/Privacy%20protection%20in%20Databases.md) +- [Privacy protection in Databases](../../../Marketing/publications/Scratch%20file/Privacy%20protection%20in%20Databases.md) - [ISO 27001 A.18.1.4 Privacy and protection of personally identifiable information](../ISO27x/legacy/ISO%2027001%202013/ISO%2027001%20A.18.1.4%20Privacy%20and%20protection%20of%20personally%20identifiable%20information.md) diff --git a/marketing/content/.DS_Store b/marketing/content/.DS_Store deleted file mode 100644 index 9720655..0000000 Binary files a/marketing/content/.DS_Store and /dev/null differ diff --git a/marketing/content/eBook-Audit/.DS_Store b/marketing/content/eBook-Audit/.DS_Store deleted file mode 100644 index 37dfd52..0000000 Binary files a/marketing/content/eBook-Audit/.DS_Store and /dev/null differ diff --git a/marketing/content/eBook-Audit/.claude/settings.local.json b/marketing/content/eBook-Audit/.claude/settings.local.json deleted file mode 100644 index 3107200..0000000 --- a/marketing/content/eBook-Audit/.claude/settings.local.json +++ /dev/null @@ -1,7 +0,0 @@ -{ - "permissions": { - "allow": [ - "Bash(bash build.sh)" - ] - } -} diff --git a/marketing/content/posts/ZZP/For Leadership/s02p06nl - Bonus post Cbw en 27001.md b/marketing/content/posts/ZZP/For Leadership/s02p06nl - Bonus post Cbw en 27001.md deleted file mode 100644 index be4c82f..0000000 --- a/marketing/content/posts/ZZP/For Leadership/s02p06nl - Bonus post Cbw en 27001.md +++ /dev/null @@ -1,3 +0,0 @@ - - -β€” Cbw-compliance in 8 stappen β€” 5/5 \#managingsecurity \#Cbw \#NIS2 \ No newline at end of file diff --git a/marketing/content/posts/ZZP/For Leadership/s02pxxnl - Er is geen diploma voor Cbw-compliance.md b/marketing/content/posts/ZZP/For Leadership/s02pxxnl - Er is geen diploma voor Cbw-compliance.md deleted file mode 100644 index 9dab054..0000000 --- a/marketing/content/posts/ZZP/For Leadership/s02pxxnl - Er is geen diploma voor Cbw-compliance.md +++ /dev/null @@ -1,3 +0,0 @@ -Er is geen diploma voor Cbw-compliance, but the ISO 27001 comes pretty close. - -β€” Cbw-compliance in 8 stappen β€” 5/5 \#managingsecurity \#Cbw \#NIS2 \ No newline at end of file diff --git a/marketing/content/Scratch file/Data classification - how to make labels stick.md b/marketing/publications/Scratch file/Data classification - how to make labels stick.md similarity index 100% rename from marketing/content/Scratch file/Data classification - how to make labels stick.md rename to marketing/publications/Scratch file/Data classification - how to make labels stick.md diff --git a/marketing/content/Scratch file/Example of ISO 27001 mystique.md b/marketing/publications/Scratch file/Example of ISO 27001 mystique.md similarity index 100% rename from marketing/content/Scratch file/Example of ISO 27001 mystique.md rename to marketing/publications/Scratch file/Example of ISO 27001 mystique.md diff --git a/marketing/content/Scratch file/GRC software is geschreven voor domeindeskundigen.md b/marketing/publications/Scratch file/GRC software is geschreven voor domeindeskundigen.md similarity index 100% rename from marketing/content/Scratch file/GRC software is geschreven voor domeindeskundigen.md rename to marketing/publications/Scratch file/GRC software is geschreven voor domeindeskundigen.md diff --git a/marketing/content/Scratch file/Hoe dwing je verantwoordelijkheid af.md b/marketing/publications/Scratch file/Hoe dwing je verantwoordelijkheid af.md similarity index 100% rename from marketing/content/Scratch file/Hoe dwing je verantwoordelijkheid af.md rename to marketing/publications/Scratch file/Hoe dwing je verantwoordelijkheid af.md diff --git a/marketing/content/Scratch file/Least privilege, need-to-know - principles vs practice.md b/marketing/publications/Scratch file/Least privilege, need-to-know - principles vs practice.md similarity index 100% rename from marketing/content/Scratch file/Least privilege, need-to-know - principles vs practice.md rename to marketing/publications/Scratch file/Least privilege, need-to-know - principles vs practice.md diff --git a/marketing/content/Scratch file/Perverse prikkels in de normindustrie.md b/marketing/publications/Scratch file/Perverse prikkels in de normindustrie.md similarity index 100% rename from marketing/content/Scratch file/Perverse prikkels in de normindustrie.md rename to marketing/publications/Scratch file/Perverse prikkels in de normindustrie.md diff --git a/marketing/content/Scratch file/Privacy protection in Databases.md b/marketing/publications/Scratch file/Privacy protection in Databases.md similarity index 100% rename from marketing/content/Scratch file/Privacy protection in Databases.md rename to marketing/publications/Scratch file/Privacy protection in Databases.md diff --git a/marketing/content/Scratch file/Toegevoegde waarde van ISO27DIY.md b/marketing/publications/Scratch file/Toegevoegde waarde van ISO27DIY.md similarity index 100% rename from marketing/content/Scratch file/Toegevoegde waarde van ISO27DIY.md rename to marketing/publications/Scratch file/Toegevoegde waarde van ISO27DIY.md diff --git a/marketing/content/Scratch file/Voordelen van processvolwassenheid.md b/marketing/publications/Scratch file/Voordelen van processvolwassenheid.md similarity index 100% rename from marketing/content/Scratch file/Voordelen van processvolwassenheid.md rename to marketing/publications/Scratch file/Voordelen van processvolwassenheid.md diff --git a/marketing/content/Scratch file/Weerbaarheid - bereid je voor op verstoring.md b/marketing/publications/Scratch file/Weerbaarheid - bereid je voor op verstoring.md similarity index 100% rename from marketing/content/Scratch file/Weerbaarheid - bereid je voor op verstoring.md rename to marketing/publications/Scratch file/Weerbaarheid - bereid je voor op verstoring.md diff --git a/marketing/content/Scratch file/longlist.md b/marketing/publications/Scratch file/longlist.md similarity index 100% rename from marketing/content/Scratch file/longlist.md rename to marketing/publications/Scratch file/longlist.md diff --git a/marketing/publications/Scratch file/startproblemen of vastloper.md b/marketing/publications/Scratch file/startproblemen of vastloper.md new file mode 100644 index 0000000..3527971 --- /dev/null +++ b/marketing/publications/Scratch file/startproblemen of vastloper.md @@ -0,0 +1,15 @@ + +Vastgelopen met je ISO 27001 implementatie? Komt je SIO 27001 implementatie niet van de grond? Ik kan je helpen + +Wie moet je erbij betrekken? +Wie moet je verantwoordelijk maken? +Hoeveel tijd moet je vrijmaken? +Welke tooling is nodig +Moet jhe een consultant inhuren ? +Wie maak je projectmanager? +Waar moet je beginnen? +Moet je alle controls implementeren? +Loopt de boel niet vast in eindeloze procedures? +Wordt het niet veel te bureacratisch +Mensen szien de noodzaak niet +IT werkt tegen diff --git a/marketing/content/eBook-Audit/Alles over de Audit - structuur.md b/marketing/publications/eBook-Audit/Alles over de Audit - structuur.md similarity index 100% rename from marketing/content/eBook-Audit/Alles over de Audit - structuur.md rename to marketing/publications/eBook-Audit/Alles over de Audit - structuur.md diff --git a/marketing/content/eBook-Audit/Alles wat je wilt weten over de ISO 27001 audit.md b/marketing/publications/eBook-Audit/Alles wat je wilt weten over de ISO 27001 audit.md similarity index 100% rename from marketing/content/eBook-Audit/Alles wat je wilt weten over de ISO 27001 audit.md rename to marketing/publications/eBook-Audit/Alles wat je wilt weten over de ISO 27001 audit.md diff --git a/marketing/content/eBook-Audit/Angsten over de audit.md b/marketing/publications/eBook-Audit/Angsten over de audit.md similarity index 100% rename from marketing/content/eBook-Audit/Angsten over de audit.md rename to marketing/publications/eBook-Audit/Angsten over de audit.md diff --git a/marketing/content/eBook-Audit/Hoe bereid je je voor.md b/marketing/publications/eBook-Audit/Hoe bereid je je voor.md similarity index 100% rename from marketing/content/eBook-Audit/Hoe bereid je je voor.md rename to marketing/publications/eBook-Audit/Hoe bereid je je voor.md diff --git a/marketing/content/eBook-Audit/Hoe technisch is de audit.md b/marketing/publications/eBook-Audit/Hoe technisch is de audit.md similarity index 100% rename from marketing/content/eBook-Audit/Hoe technisch is de audit.md rename to marketing/publications/eBook-Audit/Hoe technisch is de audit.md diff --git a/marketing/content/eBook-Audit/ISO27DIY-ebook.pdf b/marketing/publications/eBook-Audit/ISO27DIY-ebook.pdf similarity index 100% rename from marketing/content/eBook-Audit/ISO27DIY-ebook.pdf rename to marketing/publications/eBook-Audit/ISO27DIY-ebook.pdf diff --git a/marketing/content/eBook-Audit/Wie moeten er aanwezig zijn.md b/marketing/publications/eBook-Audit/Wie moeten er aanwezig zijn.md similarity index 100% rename from marketing/content/eBook-Audit/Wie moeten er aanwezig zijn.md rename to marketing/publications/eBook-Audit/Wie moeten er aanwezig zijn.md diff --git a/marketing/content/eBook-Audit/assets/ISO27DIY_LOGO_rgb_transparant.png b/marketing/publications/eBook-Audit/assets/ISO27DIY_LOGO_rgb_transparant.png similarity index 100% rename from marketing/content/eBook-Audit/assets/ISO27DIY_LOGO_rgb_transparant.png rename to marketing/publications/eBook-Audit/assets/ISO27DIY_LOGO_rgb_transparant.png diff --git a/marketing/content/eBook-Audit/assets/ISO27DIY_Logo_in_white_circle.png b/marketing/publications/eBook-Audit/assets/ISO27DIY_Logo_in_white_circle.png similarity index 100% rename from marketing/content/eBook-Audit/assets/ISO27DIY_Logo_in_white_circle.png rename to marketing/publications/eBook-Audit/assets/ISO27DIY_Logo_in_white_circle.png diff --git a/marketing/content/eBook-Audit/build.sh b/marketing/publications/eBook-Audit/build.sh similarity index 100% rename from marketing/content/eBook-Audit/build.sh rename to marketing/publications/eBook-Audit/build.sh diff --git a/marketing/content/eBook-Audit/eBook download triggers.md b/marketing/publications/eBook-Audit/eBook download triggers.md similarity index 100% rename from marketing/content/eBook-Audit/eBook download triggers.md rename to marketing/publications/eBook-Audit/eBook download triggers.md diff --git a/marketing/content/eBook-Audit/ebook-design-reference.html b/marketing/publications/eBook-Audit/ebook-design-reference.html similarity index 100% rename from marketing/content/eBook-Audit/ebook-design-reference.html rename to marketing/publications/eBook-Audit/ebook-design-reference.html diff --git a/marketing/content/eBook-Audit/ebook-design-reference2.html b/marketing/publications/eBook-Audit/ebook-design-reference2.html similarity index 100% rename from marketing/content/eBook-Audit/ebook-design-reference2.html rename to marketing/publications/eBook-Audit/ebook-design-reference2.html diff --git a/marketing/content/eBook-Audit/ebook-iso27001-audit.md b/marketing/publications/eBook-Audit/ebook-iso27001-audit.md similarity index 100% rename from marketing/content/eBook-Audit/ebook-iso27001-audit.md rename to marketing/publications/eBook-Audit/ebook-iso27001-audit.md diff --git a/marketing/content/eBook-Audit/iso27diy-book.tex b/marketing/publications/eBook-Audit/iso27diy-book.tex similarity index 100% rename from marketing/content/eBook-Audit/iso27diy-book.tex rename to marketing/publications/eBook-Audit/iso27diy-book.tex diff --git a/marketing/content/posts/ZZP/AuditLens CISO agents.md b/marketing/publications/posts/AuditLens CISO agents.md similarity index 100% rename from marketing/content/posts/ZZP/AuditLens CISO agents.md rename to marketing/publications/posts/AuditLens CISO agents.md diff --git a/marketing/content/posts/ZZP/AuditLens-agents-diagram.jpeg b/marketing/publications/posts/AuditLens-agents-diagram.jpeg similarity index 100% rename from marketing/content/posts/ZZP/AuditLens-agents-diagram.jpeg rename to marketing/publications/posts/AuditLens-agents-diagram.jpeg diff --git a/marketing/content/posts/ZZP/For MSPs/Do you supply EU customers.md b/marketing/publications/posts/Do you supply EU customers.md similarity index 86% rename from marketing/content/posts/ZZP/For MSPs/Do you supply EU customers.md rename to marketing/publications/posts/Do you supply EU customers.md index db69e16..45104ed 100644 --- a/marketing/content/posts/ZZP/For MSPs/Do you supply EU customers.md +++ b/marketing/publications/posts/Do you supply EU customers.md @@ -1,3 +1,26 @@ +--- +title: "Do you supply EU customers in vital sectors?" +language: en + +proposition: advisory + +audience: + - msp + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: draft + +notetype: publication +isotags: [] +tags: [] +--- + **Do you supply EU customers in vital sectors? They will send you this checklist.** The EU Cybersecurity Act (NIS2) is now being implemented across member states of the European Union. One of its core requirements: supply chain responsibility. Organizations that fall under the law are legally obligated to assess the security posture of their suppliers β€” and to contractually enforce minimum standards. diff --git a/marketing/content/posts/ZZP/You can't automate ISO 27001 compliance.md b/marketing/publications/posts/You can't automate ISO 27001 compliance.md similarity index 88% rename from marketing/content/posts/ZZP/You can't automate ISO 27001 compliance.md rename to marketing/publications/posts/You can't automate ISO 27001 compliance.md index 2226d37..e68760b 100644 --- a/marketing/content/posts/ZZP/You can't automate ISO 27001 compliance.md +++ b/marketing/publications/posts/You can't automate ISO 27001 compliance.md @@ -1,3 +1,26 @@ +--- +title: "Sorry, but you can't automate ISO 27001 compliance" +language: en + +proposition: advisory + +audience: + - general + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: draft + +notetype: publication +isotags: [] +tags: [] +--- + **Sorry, but you can't automate ISO 27001 compliance** Some vendors promise ISO 27001 certification at next to nothing, through the use of AI. Cheap, fast, and effortless. If it sounds too good to be true, it probably is. diff --git a/marketing/content/posts/agent-instructie.md b/marketing/publications/posts/agent-instructie.md similarity index 100% rename from marketing/content/posts/agent-instructie.md rename to marketing/publications/posts/agent-instructie.md diff --git a/marketing/content/posts/richard-context.md b/marketing/publications/posts/richard-context.md similarity index 100% rename from marketing/content/posts/richard-context.md rename to marketing/publications/posts/richard-context.md diff --git a/marketing/content/posts/ZZP/For Leadership/s01p01en - IT is not going to fix your security problem.md b/marketing/publications/posts/s01p01en - IT is not going to fix your security problem.md similarity index 62% rename from marketing/content/posts/ZZP/For Leadership/s01p01en - IT is not going to fix your security problem.md rename to marketing/publications/posts/s01p01en - IT is not going to fix your security problem.md index 027d482..ee4fe4c 100644 --- a/marketing/content/posts/ZZP/For Leadership/s01p01en - IT is not going to fix your security problem.md +++ b/marketing/publications/posts/s01p01en - IT is not going to fix your security problem.md @@ -1,3 +1,36 @@ +--- +title: "IT is not going to fix your security problem" +language: en + +proposition: advisory + +series-id: s01 +series-title: "Security as an organisational challenge" +series-part: 1 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-13T17:30:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-activity-7460380869439016960-G-7x" + +notetype: publication +isotags: [] +tags: [] +--- + `Posted on 13 May 2026 19:30 CEST to LinkedIn personal stream` # IT is not going to fix your security problem @@ -5,10 +38,10 @@ IT is not going to fix your security. Not because they don't want to. Not because they lack technical skills. But because essential parts of information security are out of scope for the IT department. -Here’s what I see in practice:. +Here's what I see in practice:. - A website developer temporarily shares admin rights with an external consultant to troubleshoot an integration. - The account of the maintenance engineer that left the company last year is still being used. -- A sales agent in Brazil gets full access to the company’s CRM, despite operating under a different legal framework. +- A sales agent in Brazil gets full access to the company's CRM, despite operating under a different legal framework. Examples of non-trivial information security risks arising in day-to-day operations. They cannot be fixed by technical solutions. Why? Because they're management issues, not IT problems. @@ -21,4 +54,4 @@ Which questions are not being asked in your organization? β€” Security as an organizational challenge β€” post 1/3 -**#managingsecurity** \ No newline at end of file +**#managingsecurity** diff --git a/marketing/content/posts/ZZP/For Leadership/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md b/marketing/publications/posts/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md similarity index 71% rename from marketing/content/posts/ZZP/For Leadership/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md rename to marketing/publications/posts/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md index ad1f50a..2c5d3ea 100644 --- a/marketing/content/posts/ZZP/For Leadership/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md +++ b/marketing/publications/posts/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md @@ -1,3 +1,36 @@ +--- +title: "De IT afdeling gaat jouw beveiliging niet op orde krijgen" +language: nl + +proposition: advisory + +series-id: s01 +series-title: "Security als managementvraagstuk" +series-part: 1 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-13T08:30:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-activity-7460245060933136384-IiMo" + +notetype: publication +isotags: [] +tags: [] +--- + `posted on 13 May 2026 10:30 CEST to LinkedIn personal stream` # De IT afdeling gaat jouw beveiliging niet op orde krijgen @@ -15,4 +48,4 @@ Welke vragen worden in jouw organisatie niet gesteld? β€” Security als managementvraagstuk β€” post 1/3 -**#managingsecurity** \ No newline at end of file +**#managingsecurity** diff --git a/marketing/content/posts/ZZP/For Leadership/s01p02en - All security risks start with a decision.md b/marketing/publications/posts/s01p02en - All security risks start with a decision.md similarity index 77% rename from marketing/content/posts/ZZP/For Leadership/s01p02en - All security risks start with a decision.md rename to marketing/publications/posts/s01p02en - All security risks start with a decision.md index 894f481..019ca07 100644 --- a/marketing/content/posts/ZZP/For Leadership/s01p02en - All security risks start with a decision.md +++ b/marketing/publications/posts/s01p02en - All security risks start with a decision.md @@ -1,3 +1,36 @@ +--- +title: "All security risks start with a decision" +language: en + +proposition: advisory + +series-id: s01 +series-title: "Security as an organisational challenge" +series-part: 2 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-14T17:15:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-activity-7460739462822592512-sZ68" + +notetype: publication +isotags: [] +tags: [] +--- + `Posted on 14 May 2026 19:15 CEST to LinkedIn personal stream` # All security risks start with a decision @@ -22,4 +55,4 @@ Don't just ask the question: "How will we make this a success?", but also ask: " β€” Security as an organizational challenge β€” post 2/3 -**#managingsecurity** \ No newline at end of file +**#managingsecurity** diff --git a/marketing/content/posts/ZZP/For Leadership/s01p02nl - Een beveiligingsrisico begint met een beslissing.md b/marketing/publications/posts/s01p02nl - Een beveiligingsrisico begint met een beslissing.md similarity index 78% rename from marketing/content/posts/ZZP/For Leadership/s01p02nl - Een beveiligingsrisico begint met een beslissing.md rename to marketing/publications/posts/s01p02nl - Een beveiligingsrisico begint met een beslissing.md index b8a9003..7e01980 100644 --- a/marketing/content/posts/ZZP/For Leadership/s01p02nl - Een beveiligingsrisico begint met een beslissing.md +++ b/marketing/publications/posts/s01p02nl - Een beveiligingsrisico begint met een beslissing.md @@ -1,3 +1,36 @@ +--- +title: "Een beveiligingsrisico begint met een beslissing" +language: nl + +proposition: advisory + +series-id: s01 +series-title: "Security als managementvraagstuk" +series-part: 2 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-18T08:15:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-activity-7462053131720413185-S-oH" + +notetype: publication +isotags: [] +tags: [] +--- + `posted on 18 May 2026 10:15 CEST to LinkedIn personal stream` # Een beveiligingsrisico begint met een beslissing @@ -22,4 +55,4 @@ Stel niet alleen de vraag: "hoe maken we dit tot een succes?", maar vraag ook: " β€” Security als managementvraagstuk β€” 2/3 -\#managingsecurity \ No newline at end of file +\#managingsecurity diff --git a/marketing/content/posts/ZZP/For Leadership/s01p03en - Security is a management issue.md b/marketing/publications/posts/s01p03en - Security is a management issue.md similarity index 68% rename from marketing/content/posts/ZZP/For Leadership/s01p03en - Security is a management issue.md rename to marketing/publications/posts/s01p03en - Security is a management issue.md index 042ecf1..2bc39f3 100644 --- a/marketing/content/posts/ZZP/For Leadership/s01p03en - Security is a management issue.md +++ b/marketing/publications/posts/s01p03en - Security is a management issue.md @@ -1,3 +1,36 @@ +--- +title: "Security isn't an IT problem, it's a management issue" +language: en + +proposition: advisory + +series-id: s01 +series-title: "Security as an organisational challenge" +series-part: 3 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-15T17:30:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-iso27001-resilience-activity-7461105663067283456-E_-F" + +notetype: publication +isotags: [] +tags: [] +--- + `Posted on 15 May 2026 19:30 CEST to LinkedIn personal stream` # Security isn't an IT problem, it's a management issue. @@ -15,4 +48,4 @@ I'd be curious to hear how that's arranged in your organization. Feel free to se β€” Security as an organizational challenge β€” 3/3 -\#managingsecurity \#iso27001 \#resilience \ No newline at end of file +\#managingsecurity \#iso27001 \#resilience diff --git a/marketing/content/posts/ZZP/For Leadership/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md b/marketing/publications/posts/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md similarity index 69% rename from marketing/content/posts/ZZP/For Leadership/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md rename to marketing/publications/posts/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md index 2760b31..6556cec 100644 --- a/marketing/content/posts/ZZP/For Leadership/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md +++ b/marketing/publications/posts/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md @@ -1,3 +1,36 @@ +--- +title: "Security is geen IT-probleem, maar een managementvraagstuk" +language: nl + +proposition: advisory + +series-id: s01 +series-title: "Security als managementvraagstuk" +series-part: 3 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-19T08:00:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-iso27001-cyberweerbaarheid-activity-7462411782574452736-VfjA" + +notetype: publication +isotags: [] +tags: [] +--- + `posted on 19 May 2026 10:00 CEST to LinkedIn personal stream` # Security is geen IT-probleem, maar een managementvraagstuk. @@ -15,4 +48,4 @@ Ik ben benieuwd hoe dat in jouw organisatie geregeld is. Stuur me gerust een ber β€” Security als managementvraagstuk β€” 3/3 -\#managingsecurity \#iso27001 \#cyberweerbaarheid \ No newline at end of file +\#managingsecurity \#iso27001 \#cyberweerbaarheid diff --git a/marketing/content/posts/ZZP/For Leadership/s01p04en - Good intentions dont scale.md b/marketing/publications/posts/s01p04en - Good intentions dont scale.md similarity index 79% rename from marketing/content/posts/ZZP/For Leadership/s01p04en - Good intentions dont scale.md rename to marketing/publications/posts/s01p04en - Good intentions dont scale.md index d477ffd..17b4a9e 100644 --- a/marketing/content/posts/ZZP/For Leadership/s01p04en - Good intentions dont scale.md +++ b/marketing/publications/posts/s01p04en - Good intentions dont scale.md @@ -1,4 +1,30 @@ -`posted on XX May 2026 XX:XX CEST to LinkedIn personal stream` +--- +title: "Good intentions don't scale" +language: en + +proposition: advisory + +series-id: s01 +series-title: "Security as an organisational challenge" +series-part: 4 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: draft + +notetype: publication +isotags: [] +tags: [] +--- + # Good intentions don't scale Good intentions don't scale. @@ -13,4 +39,4 @@ The real question isn't whether your current team is taking security seriously. How does your organization make sure security holds up when people and circumstances change? I'm curious β€” feel free to send me a message. -\#managingsecurity \#iso27001 \ No newline at end of file +\#managingsecurity \#iso27001 diff --git a/marketing/content/posts/ZZP/For Leadership/s02p01nl - Op 1 juli treedt de Cbw in werking.md b/marketing/publications/posts/s02p01nl - Op 1 juli treedt de Cbw in werking.md similarity index 71% rename from marketing/content/posts/ZZP/For Leadership/s02p01nl - Op 1 juli treedt de Cbw in werking.md rename to marketing/publications/posts/s02p01nl - Op 1 juli treedt de Cbw in werking.md index 37c1d3b..062d331 100644 --- a/marketing/content/posts/ZZP/For Leadership/s02p01nl - Op 1 juli treedt de Cbw in werking.md +++ b/marketing/publications/posts/s02p01nl - Op 1 juli treedt de Cbw in werking.md @@ -1,3 +1,36 @@ +--- +title: "Op 1 juli treedt de Cbw in werking" +language: nl + +proposition: advisory + +series-id: s02 +series-title: "Cbw-compliance in 8 stappen" +series-part: 1 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-21T08:03:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-cbw-nis2-share-7463137163187171328-OQMx/" + +notetype: publication +isotags: [] +tags: [] +--- + `posted on 21 May 2026 10:03 CEST to LinkedIn personal stream` Als bestuurder wordt jij op 1 juli 2026 persoonlijk verantwoordelijk voor informatiebeveiliging. @@ -14,4 +47,4 @@ Dat betekent dat je betrokken moet zijn bij de keuzes die op hoofdlijnen gemaakt In de komende vier posts geef ik de acht stappen die je als directie moet zetten om aan de Cbw te voldoen. Aan het eind heb je een concreet en direct uitvoerbaar stappenplan, en weet je wat er van jou als bestuurder verwacht wordt. -β€” Cbw-compliance in 8 stappen β€” 1/5 \#managingsecurity \#Cbw \#NIS2 \ No newline at end of file +β€” Cbw-compliance in 8 stappen β€” 1/5 \#managingsecurity \#Cbw \#NIS2 diff --git a/marketing/content/posts/ZZP/For Leadership/s02p02nl - Je cybersecurity hoeft niet perfect te zijn.md b/marketing/publications/posts/s02p02nl - Je cybersecurity hoeft niet perfect te zijn.md similarity index 73% rename from marketing/content/posts/ZZP/For Leadership/s02p02nl - Je cybersecurity hoeft niet perfect te zijn.md rename to marketing/publications/posts/s02p02nl - Je cybersecurity hoeft niet perfect te zijn.md index d19bf39..bb1992d 100644 --- a/marketing/content/posts/ZZP/For Leadership/s02p02nl - Je cybersecurity hoeft niet perfect te zijn.md +++ b/marketing/publications/posts/s02p02nl - Je cybersecurity hoeft niet perfect te zijn.md @@ -1,3 +1,36 @@ +--- +title: "Je cybersecurity hoeft niet perfect te zijn" +language: nl + +proposition: advisory + +series-id: s02 +series-title: "Cbw-compliance in 8 stappen" +series-part: 2 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-26T08:40:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-cbw-nis2-share-7464958267241267200-rCSz/" + +notetype: publication +isotags: [] +tags: [] +--- + `posted on 26 May 2026 10:40 CEST to LinkedIn personal stream` # Je cybersecurity hoeft niet perfect te zijn @@ -13,4 +46,4 @@ De uitkomst van de Cbw is dat informatiebeveiliging niet langer 'een IT-feestje' In de volgende post de eerste vier stappen om dit in te richten. -β€” Cbw-compliance in 8 stappen β€” 2/5 \#managingsecurity \#Cbw \#NIS2 \ No newline at end of file +β€” Cbw-compliance in 8 stappen β€” 2/5 \#managingsecurity \#Cbw \#NIS2 diff --git a/marketing/content/posts/ZZP/For Leadership/s02p03nl - Waar begin je?.md b/marketing/publications/posts/s02p03nl - Waar begin je?.md similarity index 81% rename from marketing/content/posts/ZZP/For Leadership/s02p03nl - Waar begin je?.md rename to marketing/publications/posts/s02p03nl - Waar begin je?.md index 3600a07..0653417 100644 --- a/marketing/content/posts/ZZP/For Leadership/s02p03nl - Waar begin je?.md +++ b/marketing/publications/posts/s02p03nl - Waar begin je?.md @@ -1,3 +1,36 @@ +--- +title: "De Cbw voor bestuurders: waar begin je?" +language: nl + +proposition: advisory + +series-id: s02 +series-title: "Cbw-compliance in 8 stappen" +series-part: 3 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-27T08:22:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-cbw-nis2-share-7465316450682011650-lg9O/" + +notetype: publication +isotags: [] +tags: [] +--- + `posted on 27 May 2026 10:22 CEST to LinkedIn personal stream` # De Cbw voor bestuurders: waar begin je? @@ -17,4 +50,4 @@ Stap 4: Incident response β€” Als er iets misgaat, moet er een plan liggen. Dan Deze vier stappen zorgen voor inzicht en vertrouwen. In de volgende post de vier stappen die informatiebeveiliging compliant en aantoonbaar maken. -β€” Cbw-compliance in 8 stappen β€” 3/5 \#managingsecurity \#Cbw \#NIS2 \ No newline at end of file +β€” Cbw-compliance in 8 stappen β€” 3/5 \#managingsecurity \#Cbw \#NIS2 diff --git a/marketing/content/posts/ZZP/For Leadership/s02p04nl - Hoe kun je als bestuurder aantonen dat je voldoet aan de Cbw.md b/marketing/publications/posts/s02p04nl - Hoe kun je als bestuurder aantonen dat je voldoet aan de Cbw.md similarity index 81% rename from marketing/content/posts/ZZP/For Leadership/s02p04nl - Hoe kun je als bestuurder aantonen dat je voldoet aan de Cbw.md rename to marketing/publications/posts/s02p04nl - Hoe kun je als bestuurder aantonen dat je voldoet aan de Cbw.md index 89640de..cc74a64 100644 --- a/marketing/content/posts/ZZP/For Leadership/s02p04nl - Hoe kun je als bestuurder aantonen dat je voldoet aan de Cbw.md +++ b/marketing/publications/posts/s02p04nl - Hoe kun je als bestuurder aantonen dat je voldoet aan de Cbw.md @@ -1,3 +1,36 @@ +--- +title: "Hoe kun je als bestuurder aantonen dat je voldoet aan de Cbw?" +language: nl + +proposition: advisory + +series-id: s02 +series-title: "Cbw-compliance in 8 stappen" +series-part: 4 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-05-28T08:33:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-cbw-nis2-share-7465681697880035329-E7VV/" + +notetype: publication +isotags: [] +tags: [] +--- + `posted on 28 May 2026 10:33 CEST to LinkedIn personal stream` # Hoe kun je als bestuurder aantonen dat je voldoet aan de Cbw? @@ -16,4 +49,4 @@ Stap 8: Borging in de organisatie β€” Voldoen aan de Cbw is geen eenmalig projec In de volgende post: Cbw compliance heeft geen finishlijn, maar vraagt wel voortdurende aandacht. -β€” Cbw-compliance in 8 stappen β€” 4/5 \#managingsecurity \#Cbw \#NIS2 \#Compliance \ No newline at end of file +β€” Cbw-compliance in 8 stappen β€” 4/5 \#managingsecurity \#Cbw \#NIS2 \#Compliance diff --git a/marketing/content/posts/ZZP/For Leadership/s02p05nl - De Cbw is geen project.md b/marketing/publications/posts/s02p05nl - De Cbw is geen project.md similarity index 70% rename from marketing/content/posts/ZZP/For Leadership/s02p05nl - De Cbw is geen project.md rename to marketing/publications/posts/s02p05nl - De Cbw is geen project.md index f821332..a7ffa9a 100644 --- a/marketing/content/posts/ZZP/For Leadership/s02p05nl - De Cbw is geen project.md +++ b/marketing/publications/posts/s02p05nl - De Cbw is geen project.md @@ -1,3 +1,38 @@ +--- +title: "De Cbw is geen project!" +language: nl + +proposition: advisory + +series-id: s02 +series-title: "Cbw-compliance in 8 stappen" +series-part: 5 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: published + +publish-dates: + linkedin: 2026-06-01T13:31:00Z + +published-urls: + linkedin: "https://www.linkedin.com/posts/richardkranendonk_managingsecurity-cbw-nis2-activity-7467206197365030912-E-pn" + +notetype: publication +isotags: [] +tags: [] +--- + +`posted on 1 June 2026 15:31 CEST to LinkedIn personal stream` + # De Cbw is geen project! Cbw compliance is geen project, maar vraagt van jou als bestuurder voortdurende aandacht. @@ -14,4 +49,4 @@ Als je wilt weten waar jouw organisatie staat, praat ik graag een uur met je. β€” Cbw-compliance in 8 stappen β€” 5/5 \#managingsecurity \#Cbw \#NIS2 -Vorige post hier: https://www.linkedin.com/posts/richardkranendonk_managingsecurity-cbw-nis2-activity-7465681698601566209-Do6v \ No newline at end of file +Vorige post hier: https://www.linkedin.com/posts/richardkranendonk_managingsecurity-cbw-nis2-activity-7465681698601566209-Do6v diff --git a/marketing/publications/posts/s02p06nl - Bonus post Cbw en 27001.md b/marketing/publications/posts/s02p06nl - Bonus post Cbw en 27001.md new file mode 100644 index 0000000..28fa3b4 --- /dev/null +++ b/marketing/publications/posts/s02p06nl - Bonus post Cbw en 27001.md @@ -0,0 +1,28 @@ +--- +title: "Bonus post: Cbw en ISO 27001" +language: nl + +proposition: advisory + +series-id: s02 +series-title: "Cbw-compliance in 8 stappen" +series-part: 6 + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: draft + +notetype: publication +isotags: [] +tags: [] +--- + +β€” Cbw-compliance in 8 stappen β€” 5/5 \#managingsecurity \#Cbw \#NIS2 diff --git a/marketing/publications/posts/s02pxxnl - Er is geen diploma voor Cbw-compliance.md b/marketing/publications/posts/s02pxxnl - Er is geen diploma voor Cbw-compliance.md new file mode 100644 index 0000000..9b1310e --- /dev/null +++ b/marketing/publications/posts/s02pxxnl - Er is geen diploma voor Cbw-compliance.md @@ -0,0 +1,30 @@ +--- +title: "Er is geen diploma voor Cbw-compliance" +language: nl + +proposition: advisory + +series-id: s02 +series-title: "Cbw-compliance in 8 stappen" +series-part: null + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: draft + +notetype: publication +isotags: [] +tags: [] +--- + +Er is geen diploma voor Cbw-compliance, but the ISO 27001 comes pretty close. + +β€” Cbw-compliance in 8 stappen β€” 5/5 \#managingsecurity \#Cbw \#NIS2 diff --git a/marketing/content/posts/ZZP/For Leadership/s02pxxnl - Toch een Cbw checklist.md b/marketing/publications/posts/s02pxxnl - Toch een Cbw checklist.md similarity index 75% rename from marketing/content/posts/ZZP/For Leadership/s02pxxnl - Toch een Cbw checklist.md rename to marketing/publications/posts/s02pxxnl - Toch een Cbw checklist.md index b67fe8e..93980c8 100644 --- a/marketing/content/posts/ZZP/For Leadership/s02pxxnl - Toch een Cbw checklist.md +++ b/marketing/publications/posts/s02pxxnl - Toch een Cbw checklist.md @@ -1,3 +1,30 @@ +--- +title: "Toch een Cbw checklist" +language: nl + +proposition: advisory + +series-id: s02 +series-title: "Cbw-compliance in 8 stappen" +series-part: null + +audience: + - leadership + +channels: + - linkedin +linkedin-account: personal + +content-type: + - post + +status: draft + +notetype: publication +isotags: [] +tags: [] +--- + # De Cbw voor bestuurders: weten waar je staat vΓ³Γ³r 1 juli 2026 In mijn vorige post schreef ik, dat je de minimummaatregelen uit artikel 21 van de Cyberbeveiligingswet moet zien als een kader om te sturen in een voortdurend veranderende omgeving, en niet als een checklist voor eenmalig gebruik. @@ -13,4 +40,3 @@ Als je na de checklist graag een uurtje wilt sparren over hoe nu verder, dan pra β€” Cbw-compliance in 8 stappen β€” 5/5 \#managingsecurity \#Cbw \#NIS2 https://iso27diy.com/assets/cbw-checklist.html - diff --git a/metadata/corpus-metadata-backup.md b/metadata/corpus-metadata-backup.md new file mode 100644 index 0000000..b73e1b3 --- /dev/null +++ b/metadata/corpus-metadata-backup.md @@ -0,0 +1,97 @@ +# Corpus Metadata + +- All notes in `/Users/rico/Library/Mobile Documents/iCloud~md~obsidian/Documents/MyVault/iso27diy-corp/Corpus` need metadata. +- These metadata need to follow the [obsidian-front-matter-syntax](obsidian-front-matter-syntax.md). +- Obsidian calls metadata variables 'Properties' +- In this Corpus we use General properties (every note should have them) and specific properties (depending on the kind of note, which can be inferred from the `notetype` property, see below). + +## General properties + +**Notetype** + +The `notetype` field will have one of the following values: + +- `guide`: guided, hands-on lessons, learning by doing, interactive lessons +- `explanation`: background and context to the standards, paraphrases of the original standard texts, opinion, discussion, underlying principles, interpretation +- `application`: steps to solve a specific, real-world problem. Implementing the standard in real world environments, implementation aids, implementation examples, templates, etc. +- `reference`: secondary sources of information, like original standard texts, dictionaries, terms and definitions. +- `publication`: for content created by TSW for publication, e.g. articles, eBooks, social media posts. +- `other`: for all notes that, by there content, cannot be placed in one for the previous categories. +- `iso27diyGIS`: notes that belong to the ISO27DIY Guided Implementation System (GIS). + +**Language** + +- For the `language` property we use the language code as defined in ISO 639-1. + +**Isotags** + +The property `isotags`, of type list, allows any note to be linked to clauses and controls of the ISO 27001 / ISO 27002 standard, by the `id` property of the Original Standard Texts, found in `Corpus/Standards/ISO27x/OST/27001/EN` and `/Corpus/Standards/ISO27x/OST/27002/EN`, respectively. + +For example, a note that needs to be linked to ISO 27001 clause 5.2 Policy, will get a value of `C.5.2` added to its `isotags` list. Likewise, a note that needs to be linked to ISO 27002 control 5.15 Access control, will get a value of `A.5.15` added to its `isotags` list. + +## Properties for ISO 27001 and 27002 Original Standard Texts + +Original Standard Texts are found in `Corpus/Standards/ISO27x/OST/` . + +*Important: the body of these notes must never be changed!* + +OST notes inherit the general properties, and also have the following properties: + +- `status`: as of yet, the only value defined for the property is `active`. I foresee a `superseded` or `replaced` status for later. +- `sourcetext`: the standard name and version, e.g. `iso27001:en:2022` + +The OST/27002 have specific properties deduced from chapter 4 of the standard ("Themes and Attributes"). They are: +- `theme` +- `control_type` +- `information_security_properties` +- `cybersecurity_concepts` +- `operational_capabilities` +- `security_domains`. + +For the possible values of these properties, see [themes-and-attributes-in-iso-27002](themes-and-attributes-in-iso-27002.md). + +## Properties for the ISO27DIY Guided Implementation System + +- Notes in the `iso27DIY-gis` folder and subfolders are of `notetype` `iso27diyGIS`. +- Notes in the `iso27DIY-gis/guide` subfolder ... +- Notes in the `iso27DIY-gis/reference` subfolder ... + +## Properties for Publications + +- publications can be found in `iso27diy-corp/Marketing/publications` and are of `notetype` `publication` + + +``` +--- +title: "" # post title +series: "" # series title +series-slug: "" # series title as a slug, e.g. "access-control-basics" +series-part: 1 # position within the series; omit if standalone +theme: "" # broader topic cluster, e.g. "ISO27001 myths" +channels: # list β€” a post can go to multiple channels + - linkedin + - newsletter + - blog +status: draft # draft | ready | scheduled | published +publish-dates: # ISO 8601, e.g. 2026-06-10; can be a list if channels differ + linkedin: 2026-06-10 + newsletter: 2026-06-17 + blog: 2026-06-17 +published-urls: # fill in after publishing; one per channel + linkedin: "" + blog: "" +content-type: "" # post | article | newsletter-section | thread +source-notes: # vault notes this was drawn from + - "[[path/to/note]]" +tags: [] + +notetype: publication +isotags: +iso-id +audience + +--- +``` + + + diff --git a/metadata/corpus-metadata.md b/metadata/corpus-metadata.md index 5851a52..0aad696 100644 --- a/metadata/corpus-metadata.md +++ b/metadata/corpus-metadata.md @@ -1,37 +1,143 @@ # Corpus Metadata -- All notes in this Obsidian vault need metadata. +- All notes in `/Users/rico/Library/Mobile Documents/iCloud~md~obsidian/Documents/MyVault/iso27diy-corp/Corpus` need metadata. - These metadata need to follow the [obsidian-front-matter-syntax](obsidian-front-matter-syntax.md). - Obsidian calls metadata variables 'Properties' -- In this Corpus we use General properties (every note should have them) and Specific properties (depending on the kind of note, can be inferred from other properties) +- In this Corpus we use General properties (every note should have them) and specific properties (depending on the kind of note, which can be inferred from the `notetype` property, see below). -## General metadata +## General properties -### Notetype +**Notetype** The `notetype` field will have one of the following values: + - `guide`: guided, hands-on lessons, learning by doing, interactive lessons - `explanation`: background and context to the standards, paraphrases of the original standard texts, opinion, discussion, underlying principles, interpretation - `application`: steps to solve a specific, real-world problem. Implementing the standard in real world environments, implementation aids, implementation examples, templates, etc. -- `reference`: for original standard texts, dictionaries, terms and definitions. -- `other`: for all notes that, by there content, cannot be placed in one for the previous categories. +- `reference`: secondary sources of information, like original standard texts, dictionaries, terms and definitions. +- `publication`: for content created by TSW for publication, e.g. articles, eBooks, social media posts. +- `other`: for all notes that, by their content, cannot be placed in one of the previous categories. +- `iso27diyGIS`: notes that belong to the ISO27DIY Guided Implementation System (GIS). -Note: -- Notes in the iso27DIY-gis/guide folder and subfolders are typically of the `guide` type. -- Notes in iso27DIY-gis/reference and subfolders are typically of the `explanation` or `application` type. +**Language** -### Language -For the `language` property we use the language code as defined in ISO 639-1. +- For the `language` property we use the language code as defined in ISO 639-1. + +**Isotags** -### Status -As of yet, the only value defined for the `status` property is `active`. -## Isotags The property `isotags`, of type list, allows any note to be linked to clauses and controls of the ISO 27001 / ISO 27002 standard, by the `id` property of the Original Standard Texts, found in `Corpus/Standards/ISO27x/OST/27001/EN` and `/Corpus/Standards/ISO27x/OST/27002/EN`, respectively. -For example, a note that needs to be linked to ISO 27001 clause 5.2 Policy, will get a value of C.5.2 added to its `isotags` list. Likewise, a note that needs to be linked to ISO 27002 control 5.15 Access control, will get a value of A.5.15 added to its `isotags` list. -## Metadata for ISO 27001 and 27002 Original Standard Texts -- The original texts of the ISO 27001 and ISO 27002 standards can be found in the OST folder and subfolders. -- These notes are tagged with β€œsourcetext”. -- The body of these notes must never be changed! -- Specific properties for ISO 27002 OST notes are deduced from chapter 4 of the standard ("Themes and Attributes"). They are: `theme`, `control_type`, `information_security_properties`, `cybersecurity_concepts`, `operational_capabilities`, and `security_domains`. -- For the possible values of these properties, see [themes-and-attributes-in-iso-27002](themes-and-attributes-in-iso-27002.md). +For example, a note that needs to be linked to ISO 27001 clause 5.2 Policy, will get a value of `C.5.2` added to its `isotags` list. Likewise, a note that needs to be linked to ISO 27002 control 5.15 Access control, will get a value of `A.5.15` added to its `isotags` list. + +## Properties for ISO 27001 and 27002 Original Standard Texts + +Original Standard Texts are found in `Corpus/Standards/ISO27x/OST/` . + +*Important: the body of these notes must never be changed!* + +OST notes inherit the general properties, and also have the following properties: + +- `status`: as of yet, the only value defined for the property is `active`. I foresee a `superseded` or `replaced` status for later. +- `sourcetext`: the standard name and version, e.g. `iso27001:en:2022` + +The OST/27002 have specific properties deduced from chapter 4 of the standard ("Themes and Attributes"). They are: +- `theme` +- `control_type` +- `information_security_properties` +- `cybersecurity_concepts` +- `operational_capabilities` +- `security_domains` + +For the possible values of these properties, see [themes-and-attributes-in-iso-27002](themes-and-attributes-in-iso-27002.md). + +## Properties for the ISO27DIY Guided Implementation System + +- Notes in the `iso27DIY-gis` folder and subfolders are of `notetype` `iso27diyGIS`. +- Notes in the `iso27DIY-gis/guide` subfolder ... +- Notes in the `iso27DIY-gis/reference` subfolder ... + +## Properties for Publications + +Publications are found in `iso27diy-corp/Marketing/publications` and are of `notetype` `publication`. + +### Folder structure + +All publication notes live directly under `iso27diy-corp/Marketing/publications/posts/`. There are no audience or proposition subfolders β€” segmentation is handled entirely by front matter. + +### Controlled vocabularies + +**`proposition`** β€” which ISO27DIY product or practice this content promotes: +- `advisory` β€” Richard's advisory practice (ZZP) +- `canvas` β€” the Canvas Method product +- `iso27diy` β€” the ISO27DIY SaaS product + +**`audience`** β€” who the content is aimed at: +- `leadership` β€” directors, board members, senior management +- `msp` β€” managed service providers +- `technical` β€” IT professionals, security practitioners +- `general` β€” no specific segment + +**`channels`** β€” where the content is published: +- `linkedin` +- `newsletter` +- `blog` + +**`linkedin-account`** β€” which LinkedIn account was used; only relevant when `linkedin` is in `channels`: +- `personal` β€” Richard's personal LinkedIn profile +- `company` β€” ISO27DIY company page + +**`content-type`** β€” the format of the content: +- `post` +- `article` +- `newsletter-section` +- `thread` + +**`status`**: +- `draft` β€” work in progress +- `ready` β€” approved, not yet scheduled +- `scheduled` β€” publish date set +- `published` β€” live + +### Template + +```yaml +--- +title: "" # human-readable post title +language: "" # ISO 639-1 code: en | nl + +proposition: "" # advisory | canvas | iso27diy + +series-id: "" # short machine-readable code, e.g. s01, s02; omit if standalone +series-title: "" # human-readable series name; omit if standalone +series-part: # integer position within series; null if unpositioned draft; omit if standalone + +audience: # one or more of: leadership | msp | technical | general + - leadership + +channels: # one or more of: linkedin | newsletter | blog + - linkedin +linkedin-account: personal # personal | company; omit if linkedin not in channels + +content-type: # one or more of: post | article | newsletter-section | thread + - post + +status: draft # draft | ready | scheduled | published + +publish-dates: # ISO 8601 datetime in UTC, e.g. 2026-05-13T17:30:00Z + linkedin: 2026-05-13T17:30:00Z + +published-urls: # fill after publishing; omit channels not yet published + linkedin: "" + +source-notes: # optional β€” vault notes this was drawn from; omit if none + - "[[path/to/note]]" + +notetype: publication +isotags: [] # ISO 27001/27002 clause/control links; omit if not applicable +tags: [] +--- +``` + +### Filename convention + +Publication filenames follow the pattern `{series-id}p{series-part}{language} - {title-slug}.md`, e.g. `s01p01en - IT is not going to fix your security problem.md`. Standalone posts use a plain descriptive slug with no series prefix. diff --git a/metadata/front-matter-for-publications.md b/metadata/front-matter-for-publications.md index a68bc69..63b0534 100644 --- a/metadata/front-matter-for-publications.md +++ b/metadata/front-matter-for-publications.md @@ -4,43 +4,36 @@ From [claude chat](https://claude.ai/share/614ce436-307d-4740-a79f-40225461e743) ``` --- -title: "" -series: "" # slug for the series this belongs to, e.g. "access-control-basics" +title: "" # post title +series: "" # series title +series-slug: "" # series title as a slug, e.g. "access-control-basics" series-part: 1 # position within the series; omit if standalone theme: "" # broader topic cluster, e.g. "ISO27001 myths" -channel: # list β€” a post can go to multiple channels +channels: # list β€” a post can go to multiple channels - linkedin - newsletter - blog status: draft # draft | ready | scheduled | published -publish-date: # ISO 8601, e.g. 2026-06-10; can be a list if channels differ +publish-dates: # ISO 8601, e.g. 2026-06-10; can be a list if channels differ linkedin: 2026-06-10 newsletter: 2026-06-17 blog: 2026-06-17 -published-url: # fill in after publishing; one per channel +published-urls: # fill in after publishing; one per channel linkedin: "" blog: "" content-type: "" # post | article | newsletter-section | thread source-notes: # vault notes this was drawn from - "[[path/to/note]]" tags: [] + +notetype: publication +isotags: +iso-id +audience + --- ``` -### Folder structure to go with it - -``` -Content Factory/ - Publishing/ - Series/ - access-control-basics/ - part-1.md - part-2.md - Standalone/ - some-one-off-post.md -``` - -Or if you prefer tag-based grouping over folders, skip the subfolders and rely on `series` + Dataview to surface series views. --- @@ -57,8 +50,3 @@ SORT publish-date ASC --- -### Issues to flag - -- If you're already using front matter on content notes, check for conflicts with any existing `status` or `tags` fields before rolling this out. -- `published-url` will stay empty a lot. That's fine β€” it's a record, not a requirement. -- If posts get repurposed significantly between channels (not just reformatted), they probably deserve separate notes rather than one note with multiple channels listed. \ No newline at end of file