diff --git a/Content Factory/Content Factory Implementation.md b/Content Factory/Content Factory Implementation.md index 66b01eb..1651fa4 100644 --- a/Content Factory/Content Factory Implementation.md +++ b/Content Factory/Content Factory Implementation.md @@ -17,7 +17,7 @@ See [PROJECT - Five Agents](PROJECT%20-%20Five%20Agents.md) for role description - Create a single short Corpus Index Note with a list of all overview notes, with a one-line description of what they cover. - Upload the Corpus Index Note and all Overview Notes to each agent Project. Claude will read the ones it needs and ignore the rest. -See [Corpus overview notes](Corpus%20overview%20notes.md). +See [Corpus overview notes](../Corpus/Corpus%20overview%20notes.md). **3. Prepare and maintain a log** diff --git a/Content Factory/Organize your notes with Claude Code.md b/Content Factory/Organize your notes with Claude Code.md deleted file mode 100644 index d73aa24..0000000 --- a/Content Factory/Organize your notes with Claude Code.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -tags: - - prompting - - obsidian - - llm ---- -# Organize your notes with Claude Code - -Here’s what Claude Code did for me: - -- Researched best practices for note organization -- Suggested the most effective method tailored to my structure -- Tagged all my notes, created templates, added missing tags in two languages, and even built MOCs (Maps of Content) - -``` markdown - -## Instructions - -You will analyze the provided knowledge base structure and notes to create an improved organizational system. Follow these steps: - -### Phase 1: Analysis - -First, examine the current structure inside `` tags: - -**Current Organization Assessment** -- Identify the organizational method (folders, tags, links, or combination)- Note any patterns in naming conventions- Assess the depth of folder hierarchy- Identify potential information silos or duplicated content- Check for orphaned notes or broken connections - -**Content Type Classification** -- Categorize the types of notes present (reference, project, personal, etc.)- Identify recurring themes or topics- Note the average length and complexity of notes- Determine if notes follow atomic principles or contain multiple concepts - -**Usage Pattern Recognition** -- Identify how notes connect to each other- Assess the current linking strategy- Determine primary use cases (research, projects, learning, etc.) - -### Phase 2: Recommendations - -Based on your analysis, provide detailed recommendations inside `` tags: - -1. **Organizational Structure** - -Choose the most appropriate primary method: - -- **Flat structure with MOCs** (Maps of Content) for maximum flexibility -- **PARA method** (Projects, Areas, Resources, Archive) for action-oriented systems -- **Hybrid approach** combining minimal folders with extensive linking -- Justify your choice based on the user's content and patterns - -2. **Note Architecture** - -Recommend note types: - -- **Atomic notes** for single concepts -- **MOC notes** for topic organization -- **Index notes** for navigation -- **Daily notes** for capturing fleeting thoughts - -Provide templates for each recommended note type - -3. **Metadata and Tagging System** - -- Design a hierarchical tag structure using nested tags (e.g., #type/article, #status/draft) -- Recommend YAML frontmatter properties for enhanced organization -- Suggest tag categories: content type, status, topic, source - -3. **Linking Strategy** - -- Establish linking conventions -- Recommend when to use links vs. tags -- Suggest MOC creation triggers (e.g., when a topic has 5+ related notes) - -3. **Search and Retrieval Optimization** -- Recommend naming conventions for better search -- Suggest Dataview queries for dynamic organization -- Provide search operators for efficient retrieval - -### Phase 3: Implementation Plan - -Provide a step-by-step migration plan inside `` tags: - -**Preparation Phase** (Week 1) -- Backup current vault -- Install recommended plugins -- Create folder structure and initial MOCs - -**Migration Phase** (Weeks 2-3) -- Prioritize notes for migration- Update note formats and add metadata- Create connections and MOCs - -**Optimization Phase** (Week 4) -- Review and refine the system- Create documentation for future reference- Establish maintenance routines - -### Phase 4: Practical Examples - -Inside `` tags, provide: - -**Before and after** examples of note organization -**Sample MOC structure** with Dataview queries -**Template examples** for different note types -**Example tag hierarchy** specific to their content - -### Important Principles to Apply: -- **Future-proof design**: Create a system that scales with growth -- **Low-friction capture**: Ensure quick note creation without complex categorization -- **Progressive organization**: Start simple, add complexity as needed -- **Cross-referencing**: Maximize connections between related concepts -- **Regular maintenance**: Include periodic review processes - -Remember to: -- Prioritize findability over perfect categorization -- Design for the user's "worst day" when they're tired or rushed -- Balance structure with flexibility -- Incorporate both explicit (folders/tags) and implicit (links) organization -- Consider AI-assisted search capabilities in modern tools - -Your final output should be practical, actionable, and tailored to the specific content and usage patterns identified in the user's current system. -``` diff --git a/Content Factory/Corpus overview notes.md b/Corpus/Corpus overview notes.md similarity index 100% rename from Content Factory/Corpus overview notes.md rename to Corpus/Corpus overview notes.md diff --git a/Corpus/Standards/NIS 2 Cbw/Art.21 Cybersecurity risk-management measures.md b/Corpus/Standards/NIS 2 Cbw/Art.21 Cybersecurity risk-management measures.md new file mode 100644 index 0000000..40674ef --- /dev/null +++ b/Corpus/Standards/NIS 2 Cbw/Art.21 Cybersecurity risk-management measures.md @@ -0,0 +1,15 @@ +# Art.21 Cybersecurity risk-management measures + +1. Member States shall ensure that essential and important entities take appropriate and proportionate technical, operational and organisational measures to manage the risks posed to the security of network and information systems which those entities use for their operations or for the provision of their services, and to prevent or minimise the impact of incidents on recipients of their services and on other services. Taking into account the state-of-the-art and, where applicable, relevant European and international standards, as well as the cost of implementation, the measures referred to in the first subparagraph shall ensure a level of security of network and information systems appropriate to the risks posed. When assessing the proportionality of those measures, due account shall be taken of the degree of the entity’s exposure to risks, the entity’s size and the likelihood of occurrence of incidents and their severity, including their societal and economic impact. +2. The measures referred to in paragraph 1 shall be based on an all-hazards approach that aims to protect network and information systems and the physical environment of those systems from incidents, and shall include at least the following: + +- (a) policies on risk analysis and information system security; +- (b) incident handling; +- (c) business continuity, such as backup management and disaster recovery, and crisis management; +- (d) supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers; +- (e) security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure; +- (f) policies and procedures to assess the effectiveness of cybersecurity risk-management measures; +- (g) basic cyber hygiene practices and cybersecurity training; +- (h) policies and procedures regarding the use of cryptography and, where appropriate, encryption; +- (i) human resources security, access control policies and asset management; +- (j) the use of multi-factor authentication or continuous authentication solutions, secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate. diff --git a/Corpus/Standards/NIS 2 Cbw/NIS 2 Checklist artikel 21.md b/Corpus/Standards/NIS 2 Cbw/NIS 2 Checklist artikel 21 NL.md similarity index 100% rename from Corpus/Standards/NIS 2 Cbw/NIS 2 Checklist artikel 21.md rename to Corpus/Standards/NIS 2 Cbw/NIS 2 Checklist artikel 21 NL.md diff --git a/Corpus/Standards/NIS 2 Cbw/NIS 2 Index.md b/Corpus/Standards/NIS 2 Cbw/NIS 2 Index.md index 07b5e8f..00378c3 100644 --- a/Corpus/Standards/NIS 2 Cbw/NIS 2 Index.md +++ b/Corpus/Standards/NIS 2 Cbw/NIS 2 Index.md @@ -16,7 +16,7 @@ [Wetsvoorstel Cbw](Wetsvoorstel%20Cyberbeveiligingswet%20Cbw.pdf) [Blogpost - NIS 2 en de Canvas Methode](../../../Canvas%20Method/Blogpost%20-%20NIS%202%20en%20de%20Canvas%20Methode.md) -[NIS 2 Checklist artikel 21](NIS%202%20Checklist%20artikel%2021.md) +[NIS 2 Checklist artikel 21 NL](NIS%202%20Checklist%20artikel%2021%20NL.md) [NIS 2 voor Humankind](../../../Clients/Humankind/NIS%202%20voor%20Humankind.pdf) diff --git a/Corpus/Standards/NIS 2 Cbw/NIS 2 Scope.md b/Corpus/Standards/NIS 2 Cbw/NIS 2 Scope.md new file mode 100644 index 0000000..722c3d0 --- /dev/null +++ b/Corpus/Standards/NIS 2 Cbw/NIS 2 Scope.md @@ -0,0 +1,29 @@ +Here is the full list, split by annex. + +**Annex I — Sectors of High Criticality (Essential Entities)** + +1. Energy — electricity, oil, gas, hydrogen, district heating and cooling +2. Transport — air, rail, water, road +3. Banking — credit institutions +4. Financial market infrastructures — trading venues, central counterparties +5. Health — hospitals, reference laboratories, manufacturers of critical medical devices, pharmaceutical manufacturers +6. Drinking water — suppliers and distributors +7. Wastewater — collection, treatment, disposal +8. Digital infrastructure — internet exchange points, DNS providers, TLD registries, cloud computing, data centres, content delivery networks, trust service providers, electronic communications networks +9. ICT service management (B2B) — managed service providers, managed security service providers +10. Public administration — central and regional government bodies +11. Space — operators of ground-based infrastructure + +**Annex II — Other Critical Sectors (Important Entities)** + +1. Postal and courier services +2. Waste management +3. Chemicals — manufacture, production, distribution +4. Food — wholesale distribution, industrial production and processing +5. Manufacturing — medical devices, computers and electronics, electrical equipment, machinery, motor vehicles, other transport equipment +6. Digital providers — online marketplaces, online search engines, social networking platforms +7. Research organisations + +**Regardless of size — always in scope** + +DNS providers, TLD registries, trust service providers, and public electronic communications providers fall under the directive irrespective of their size. diff --git a/Corpus/Standards/NIS 2 Cbw/nis2-article21-checklist.html b/Corpus/Standards/NIS 2 Cbw/nis2-article21-checklist.html new file mode 100644 index 0000000..c12436f --- /dev/null +++ b/Corpus/Standards/NIS 2 Cbw/nis2-article21-checklist.html @@ -0,0 +1,500 @@ + + + + + +NIS2 Article 21 Checklist + + + + +
+ Progress +
+
+
+ 0 / 10 +
+ +
+
+
Directive (EU) 2022/2555 · Article 21(2)
+

NIS2 Cybersecurity Measures
Self-Assessment Checklist

+

+ The ten minimum measures required of essential and important entities under NIS2. + Use this checklist to assess your current status. Tick each item when you can demonstrate + documented, implemented, and reviewed measures — not just intent. +

+
+ +
+ +
+
+
+ Art. 21
2(a) +
+
+
+ a + Risk Analysis & Information Security Policy +
+

+ You have a documented policy covering how your organisation identifies, assesses, and manages risks to your network and information systems. The policy is approved by management, reviewed periodically, and based on a structured risk analysis — not a generic template. +

+
+
Example
+

An annual risk assessment session with department heads produces a risk register. The results inform a written information security policy, signed by the board, that is reviewed whenever significant changes occur — a new system, a new supplier, a reorganisation.

+
+
+
+ +
+
+
+ Art. 21
2(b) +
+
+
+ b + Incident Handling +
+

+ You have documented procedures for detecting, reporting, responding to, and recovering from security incidents. Staff know what constitutes an incident, who to notify, and what steps to follow. Procedures also cover the mandatory reporting obligations to national authorities under NIS2. +

+
+
Example
+

A one-page incident response procedure defines four severity levels. For significant incidents, it names the responsible person, sets a 24-hour internal escalation deadline, and references the 72-hour notification requirement to the national authority. The procedure is tested once a year in a tabletop exercise.

+
+
+
+ +
+
+
+ Art. 21
2(c) +
+
+
+ c + Business Continuity, Backup & Crisis Management +
+

+ You have a business continuity plan that covers cyber scenarios. It defines recovery time objectives (RTO) and recovery point objectives (RPO) for critical systems, documents your backup regime, and assigns responsibilities for crisis management. The plan is tested and kept current. +

+
+
Example
+

Your BCP includes a ransomware scenario: systems are unavailable for 48 hours. The plan defines which processes can continue manually, who contacts customers, and how to restore from backups. Backups are stored off-site, tested quarterly, and the maximum acceptable data loss is documented as 24 hours.

+
+
+
+ +
+
+
+ Art. 21
2(d) +
+
+
+ d + Supply Chain Security +
+

+ You assess the cybersecurity practices of your direct suppliers and service providers. You know which suppliers have access to your systems or data, what your dependency on them is, and what is contractually agreed regarding security. The security standard you apply to yourself applies equally to your supply chain. +

+
+
Example
+

You maintain a supplier register with a risk profile per vendor. Critical IT suppliers complete an annual security questionnaire. Contracts include minimum security requirements and an obligation to notify you within 24 hours of a security incident that may affect your systems.

+
+
+
+ +
+
+
+ Art. 21
2(e) +
+
+
+ e + Security in System Acquisition, Development & Maintenance +
+

+ Security requirements are built into how you procure, develop, and maintain systems — not added afterwards. This includes a process for identifying and addressing vulnerabilities in software and hardware you use, and a policy on responsible disclosure of vulnerabilities you discover. +

+
+
Example
+

Before deploying new software, your IT team runs a security review checklist. Vendors are required to provide patch timelines for known vulnerabilities. A process exists to apply critical patches within 72 hours and to track open vulnerabilities until resolved.

+
+
+
+ +
+
+
+ Art. 21
2(f) +
+
+
+ f + Effectiveness Assessment of Cybersecurity Measures +
+

+ You have a documented process to periodically evaluate whether your security measures are actually working. This is not a one-off exercise — it is a recurring review cycle (PDCA) that produces findings, decisions, and evidence. Compliance is not the goal; demonstrated effectiveness is. +

+
+
Example
+

An annual internal audit reviews a selection of security controls against the risk register. Findings are reported to the board with a remediation plan. The results of the previous year's audit are compared to track improvement over time.

+
+
+
+ +
+
+
+ Art. 21
2(g) +
+
+
+ g + Cyber Hygiene & Cybersecurity Training +
+

+ All staff are trained on basic cybersecurity practices relevant to their role. Training is recurring, not a one-off onboarding activity. You can demonstrate that training took place and that it covered current threats. A culture exists where employees feel safe reporting suspicious activity. +

+
+
Example
+

New employees complete a security awareness module within their first two weeks. All staff receive an annual refresher covering phishing, password hygiene, and what to do when something looks wrong. Participation is logged. Phishing simulations are run twice a year to test awareness in practice.

+
+
+
+ +
+
+
+ Art. 21
2(h) +
+
+
+ h + Cryptography & Encryption Policy +
+

+ You have a documented policy on the use of cryptography, covering when and how encryption is applied to data at rest and in transit. The policy specifies approved algorithms and key management practices. It is reviewed when technology or threat landscapes change. +

+
+
Example
+

Your policy states that all data classified as confidential must be encrypted at rest using AES-256, and that all external data transfers use TLS 1.2 or higher. Laptops are encrypted by default. Encryption keys are managed centrally, with access restricted to authorised personnel.

+
+
+
+ +
+
+
+ Art. 21
2(i) +
+
+
+ i + Human Resources Security, Access Control & Asset Management +
+

+ Access rights are granted on a need-to-know basis and reviewed regularly. Joiners, movers, and leavers are handled through a formal process that includes timely revocation of access. You maintain an up-to-date register of information assets and know who is responsible for each one. +

+
+
Example
+

HR notifies IT on the last day of employment. The IT checklist for leavers covers revocation of all accounts, return of devices, and a brief handover conversation about tools used. Access rights are reviewed per department every six months. A simple asset register lists systems, data classifications, and owners.

+
+
+
+ +
+
+
+ Art. 21
2(j) +
+
+
+ j + Multi-Factor Authentication & Secured Communications +
+

+ Where appropriate, multi-factor authentication (MFA) is in place for access to systems and data — particularly for remote access, privileged accounts, and critical applications. Sensitive internal communications use secured channels. Emergency communication systems are documented and tested. +

+
+
Example
+

MFA is mandatory for all remote access via VPN, all cloud applications, and all accounts with administrative privileges. A policy defines which communication channels are approved for sharing confidential information. In the event of a system outage, an offline contact list and fallback procedure exists for crisis communication.

+
+
+
+ +
+ +
+ Directive (EU) 2022/2555 · Article 21(2)(a–j) + Tick only when documented, implemented, and reviewable +
+
+ + + + + diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s01p01en - IT is not going to fix your security problem.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p01en - IT is not going to fix your security problem.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s01p01en - IT is not going to fix your security problem.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p01en - IT is not going to fix your security problem.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p01nl - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s01p02en - All security risks start with a decision.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p02en - All security risks start with a decision.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s01p02en - All security risks start with a decision.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p02en - All security risks start with a decision.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s01p02nl - Een beveiligingsrisico begint met een beslissing.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p02nl - Een beveiligingsrisico begint met een beslissing.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s01p02nl - Een beveiligingsrisico begint met een beslissing.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p02nl - Een beveiligingsrisico begint met een beslissing.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s01p03en - Security is a management issue.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p03en - Security is a management issue.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s01p03en - Security is a management issue.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p03en - Security is a management issue.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p03nl - Security is geen IT-probleem, maar een managementvraagstuk.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s01p04en - Good intentions dont scale.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p04en - Good intentions dont scale.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s01p04en - Good intentions dont scale.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s01p04en - Good intentions dont scale.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s02p01nl - Op 1 juli treedt de Cbw in werking.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p01nl - Op 1 juli treedt de Cbw in werking.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s02p01nl - Op 1 juli treedt de Cbw in werking.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p01nl - Op 1 juli treedt de Cbw in werking.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s02p02nl - De Cbw vraagt om risicomanagement.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p02nl - De Cbw vraagt om risicomanagement.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s02p02nl - De Cbw vraagt om risicomanagement.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p02nl - De Cbw vraagt om risicomanagement.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s02p03nl - Waar begin je?.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p03nl - Waar begin je?.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s02p03nl - Waar begin je?.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p03nl - Waar begin je?.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s02p04nl - Compliant en aantoonbaar.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p04nl - Compliant en aantoonbaar.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s02p04nl - Compliant en aantoonbaar.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p04nl - Compliant en aantoonbaar.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s02p05nl - Cbw compliance heeft geen finishlijn.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p05nl - Cbw compliance heeft geen finishlijn.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s02p05nl - Cbw compliance heeft geen finishlijn.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p05nl - Cbw compliance heeft geen finishlijn.md diff --git a/Content Factory/Marketing voor ZZP werk/Posts/s02p06nl - Bonus post Cbw en 27001.md b/marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p06nl - Bonus post Cbw en 27001.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/Posts/s02p06nl - Bonus post Cbw en 27001.md rename to marketing/Marketing voor ZZP werk/Posts/For Leadership/s02p06nl - Bonus post Cbw en 27001.md diff --git a/marketing/Marketing voor ZZP werk/Posts/For MSPs/Do you supply EU customers.md b/marketing/Marketing voor ZZP werk/Posts/For MSPs/Do you supply EU customers.md new file mode 100644 index 0000000..0118976 --- /dev/null +++ b/marketing/Marketing voor ZZP werk/Posts/For MSPs/Do you supply EU customers.md @@ -0,0 +1,18 @@ +**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. + +That means if you supply to organizations in sectors that have been marked 'essential' or 'important' — like energy, healthcare, manufacturing, food, B2B IT services and cloud computing —, your customers will be asking you to demonstrate that your information security is in order. Not as a choice, but because the law requires them to. (full list of sectors [here](../../../../Corpus/Standards/NIS%202%20Cbw/NIS%202%20Scope.md)) + +They will check for the minimum measures listed in Art. 21(2): + +- risk analysis, incident response procedures, and business continuity plans, covering cyber scenarios; +- management of effectiveness of cybersecurity measures; +- supply chain security and security in network and information systems acquisition; +- training of personnel and HR security; +- access control policies and asset management; +- cryptography, encryption, and the use of multi-factor authentication. + +You don't need to be certified. But you do need to be able to answer these questions — on paper, not just in your head. Have your answers ready! + +You can find an interactive checklist [[on our site]]. If the checklist raises any questions on how to continue, I'm happy to spend an hour with you. diff --git a/Content Factory/Marketing voor ZZP werk/agent-instructie.md b/marketing/Marketing voor ZZP werk/agent-instructie.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/agent-instructie.md rename to marketing/Marketing voor ZZP werk/agent-instructie.md diff --git a/Content Factory/Marketing voor ZZP werk/richard-context.md b/marketing/Marketing voor ZZP werk/richard-context.md similarity index 100% rename from Content Factory/Marketing voor ZZP werk/richard-context.md rename to marketing/Marketing voor ZZP werk/richard-context.md diff --git a/marketing/branding/Channels.md b/marketing/branding/Channels.md index 595662e..12479a0 100644 --- a/marketing/branding/Channels.md +++ b/marketing/branding/Channels.md @@ -21,3 +21,15 @@ https://www.reddit.com/r/ycombinator/s/LScdyyPYCm ISACA NOREA +## LinkedIn groepen +[Information Security Network](https://www.linkedin.com/groups/80784/) +[Information Security Community](https://www.linkedin.com/groups/38412/) +Startup Specialists Network Group +On Startups +Executive Suite +Small Business Network +Cloud Computing +Bestuurders Zorg en Welzijn +Dutch Health Network + +