<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Governance | Marcel Wiedemeier</title>
    <link>https://marcelwiedemeier.com/tags/governance/</link>
      <atom:link href="https://marcelwiedemeier.com/tags/governance/index.xml" rel="self" type="application/rss+xml" />
    <description>Governance</description>
    <generator>Wowchemy (https://wowchemy.com)</generator><language>en-US</language><copyright>© 2023</copyright><lastBuildDate>Thu, 03 May 2018 10:00:00 +0200</lastBuildDate>
    <image>
      <url>https://marcelwiedemeier.com/media/icon_hu_99437298ac1eb4c9.png</url>
      <title>Governance</title>
      <link>https://marcelwiedemeier.com/tags/governance/</link>
    </image>
    
    <item>
      <title>Beyond the Audit: Operationalizing ISO 27001 and 400&#43; Threat Vectors</title>
      <link>https://marcelwiedemeier.com/post/iso27001-certification/</link>
      <pubDate>Thu, 03 May 2018 10:00:00 +0200</pubDate>
      <guid>https://marcelwiedemeier.com/post/iso27001-certification/</guid>
      <description>&lt;p&gt;Information security certification is often treated as a superficial check-the-box compliance exercise. However, when an enterprise hosts critical digital commerce platforms, financial portals, and customer data for leading European brands, security must be an active, living operational discipline.&lt;/p&gt;
&lt;p&gt;As the sponsor and driver of the &lt;strong&gt;ISO 27001 certification&lt;/strong&gt; program for the Unic Service Business, I directed the strategy, risk modeling, process re-engineering, employee training, and external audit necessary to achieve formal accreditation under ISO/IEC 27001.&lt;/p&gt;
&lt;h2 id=&#34;systematic-threat-modeling-analyzing-400-risk-scenarios&#34;&gt;Systematic Threat Modeling: Analyzing 400+ Risk Scenarios&lt;/h2&gt;
&lt;p&gt;Rather than applying generic templates, we conducted a rigorous, bottom-up risk assessment evaluating over 400 distinct threat vectors across infrastructure, software supply chain, personnel, and physical environments:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;+-----------------------------------------------------------------------------------------+
|                        ISO 27001 Information Security Architecture                      |
|                                                                                         |
|  +---------------------+    Threat &amp;amp; Vulnerability Analysis     +--------------------+  |
|  | Context &amp;amp; Assets    | -------------------------------------&amp;gt; | 400+ Risk Matrix   |  |
|  | - Web Infrastructure|                                        | - Likelihood (1-5) |  |
|  | - Client Databases  |                                        | - Impact (1-5)     |  |
|  | - CI/CD Pipelines   |                                        | - Risk Score (1-25)|  |
|  +---------------------+                                        +--------------------+  |
|                                                                            |            |
|                                        Risk Treatment &amp;amp; Controls Selection |            |
|                                                                            v            |
|  +-----------------------------------------------------------------------------------+  |
|  | Annex A Security Controls Implementation:                                         |  |
|  | * A.9 Access Control: Zero-trust RBAC, MFA, privileged access management (PAM)    |  |
|  | * A.12 Operations Security: Automated patch management, malware defense, logging |  |
|  | * A.14 System Acquisition &amp;amp; Dev: Static code analysis (SAST), secrets management  |  |
|  | * A.16 Incident Management: Major incident playbooks, tabletop drills             |  |
|  | * A.17 Business Continuity: Redundant multi-region failover, verified backups    |  |
|  +-----------------------------------------------------------------------------------+  |
|                                            |                                            |
|                                            v Continuous Monitoring &amp;amp; Audit              |
|  +-----------------------------------------------------------------------------------+  |
|  | Independent Third-Party Certification (Accredited External Auditors)              |  |
|  +-----------------------------------------------------------------------------------+  |
+-----------------------------------------------------------------------------------------+
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;key-operational-transformations&#34;&gt;Key Operational Transformations&lt;/h2&gt;
&lt;p&gt;To meet and exceed ISO 27001 standards, we introduced foundational architectural and operational enhancements:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Privileged Access Management &amp;amp; Zero Standing Privileges&lt;/strong&gt;: Eliminated shared administrative root accounts. All engineer access to production servers was routed through audited bastion hosts requiring session recording and multi-factor authentication.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deterministic Major Incident Playbooks&lt;/strong&gt;: Developed comprehensive response workflows for Sev-1 incidents, establishing clear escalation paths, external communication protocols, forensic data preservation, and post-mortem review cycles.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automated Vulnerability Management&lt;/strong&gt;: Integrated automated vulnerability scanners into the hosting infrastructure, categorizing CVEs with strict SLA remediation targets based on CVSS severity scores.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Physical &amp;amp; Environmental Security Controls&lt;/strong&gt;: Audited and enforced strict dual-custody access controls, CCTV monitoring, and power/cooling redundancies across partner data centers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Secure Software Development Lifecycle (SSDLC)&lt;/strong&gt;: Embedded security checks, dependency scanning, and automated linting directly into GitLab CI/CD build pipelines.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;measurable-business-and-operational-impact&#34;&gt;Measurable Business and Operational Impact&lt;/h2&gt;
&lt;p&gt;Achieving ISO 27001 certification produced lasting strategic advantages for both our organization and our clients:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Customer and Partner Trust&lt;/strong&gt;: Provided enterprise clients with verifiable, accredited proof that their e-commerce and web platforms adhere to the highest international security standards.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Risk Reduction&lt;/strong&gt;: Drastically reduced the attack surface and established predictable, rapid containment protocols for potential security events.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;System Rationalization&lt;/strong&gt;: Consolidated redundant legacy hosting tools into a streamlined, audited toolchain—lowering operating costs while boosting uptime.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;By framing ISO 27001 as a blueprint for technical excellence rather than a compliance hurdle, we fostered a durable security culture that empowered our teams to deliver resilient digital experiences.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Scaling Enterprise PKI: From Manual Certificate Chaos to Automated Registration Authorities</title>
      <link>https://marcelwiedemeier.com/post/pki-enterprise/</link>
      <pubDate>Mon, 16 Apr 2018 14:00:00 +0200</pubDate>
      <guid>https://marcelwiedemeier.com/post/pki-enterprise/</guid>
      <description>&lt;p&gt;In a global enterprise operating across research institutes, manufacturing sites, and clinical trials, Public Key Infrastructure (PKI) forms the bedrock of digital trust. Digital signatures, secure email (S/MIME), device identity certificates, code signing, and internal TLS encryption all rely on the integrity of the underlying Certificate Authorities (CAs).&lt;/p&gt;
&lt;p&gt;During the Global PKI v2 initiative at Novartis International AG, we tackled the challenge of transforming a legacy, manual certificate provisioning process into an automated, web-based Registration Agency (RA) system capable of serving tens of thousands of scientists, engineers, and operational devices globally.&lt;/p&gt;
&lt;h2 id=&#34;the-pitfalls-of-legacy-enterprise-pki&#34;&gt;The Pitfalls of Legacy Enterprise PKI&lt;/h2&gt;
&lt;p&gt;Prior to PKI v2, global certificate operations faced systemic operational and security friction:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Manual Verification Bottlenecks&lt;/strong&gt;: Requesting user and server certificates required lengthy ticket-based approvals and manual identity vetting by central cryptographic administrators.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Risky Private Key Generation&lt;/strong&gt;: Users occasionally generated CSRs on untrusted endpoints with suboptimal key lengths or unvetted cryptographic algorithms.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;High Outage Risk from Manual Lifecycles&lt;/strong&gt;: Without centralized lifecycle visibility, expiring certificates frequently led to unexpected service disruptions and broken API integrations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Complex Disaster Recovery &amp;amp; Key Escrow&lt;/strong&gt;: Legacy systems lacked streamlined key recovery procedures for encrypted data, creating potential data-loss risks if user smart cards were corrupted.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;technical-architecture-of-the-web-based-registration-agency&#34;&gt;Technical Architecture of the Web-Based Registration Agency&lt;/h2&gt;
&lt;p&gt;The PKI v2 transformation centered on decoupling root and intermediate Certificate Authorities from day-to-day user interactions through a secure, multi-tier Web Registration Agency:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;+-----------------------------------------------------------------------------------------+
|                               Global Enterprise PKI Architecture                         |
|                                                                                         |
|  +--------------------+        mTLS + RBAC          +--------------------------------+  |
|  | Local IT Officer / | --------------------------&amp;gt; | Web-Based Registration Agency  |  |
|  | Automated Workload |                             | (RA Engine / Validation Logic) |  |
|  +--------------------+                             +--------------------------------+  |
|                                                                    |                    |
|                                                      Cryptographic Protocol (CMP / CMC) |
|                                                                    v                    |
|  +-----------------------------------------------------------------------------------+  |
|  | Hardened HSM-Backed Issuing Intermediate CA (Entrust Authority Security Core)      |  |
|  | - FIPS 140-2 Level 3 Hardware Security Modules                                    |  |
|  | - Automated Certificate Revocation Lists (CRL) &amp;amp; High-Availability OCSP Responders|  |
|  +-----------------------------------------------------------------------------------+  |
|                                            ^                                            |
|                                            | Air-Gapped Trust Chain                     |
|  +-----------------------------------------------------------------------------------+  |
|  | Air-Gapped Offline Root Certificate Authority                                     |  |
|  +-----------------------------------------------------------------------------------+  |
+-----------------------------------------------------------------------------------------+
&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&#34;key-security-implementations&#34;&gt;Key Security Implementations:&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;FIPS 140-2 Level 3 Hardware Security Modules (HSMs)&lt;/strong&gt;: All CA private keys were secured within dedicated physical HSMs, guaranteeing that private signing keys could never be exported in plaintext.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automated Verification Engine&lt;/strong&gt;: The new web-based RA integrated directly with enterprise directory services (LDAP/Active Directory), verifying user employment status, department authorizations, and cryptographic privilege levels in real time.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Engine-Level Template Enforcement&lt;/strong&gt;: Standardized cryptographic policies enforced minimum 2048-bit RSA / ECC key sizes, SHA-256 hashing algorithms, and strict X.509 v3 Key Usage / Extended Key Usage extensions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automated High-Performance OCSP Responders&lt;/strong&gt;: Replaced cumbersome, heavy CRL distribution points with lightweight Online Certificate Status Protocol (OCSP) responders to ensure instant revocation checks across global network perimeters.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;global-enablement--operational-transition&#34;&gt;Global Enablement &amp;amp; Operational Transition&lt;/h2&gt;
&lt;p&gt;Technology alone does not guarantee security; organizational readiness is equally crucial. We designed and delivered hands-on training programs for local IT support teams across all global regions (Europe, Americas, Asia-Pacific). This empowered local teams to safely execute authorized identity verifications while adhering to strict corporate Certificate Practice Statements (CPS).&lt;/p&gt;
&lt;p&gt;By transitioning PKI from an isolated project into an enterprise operational service, we delivered high-assurance digital identities with zero downtime and established a secure foundation for enterprise-wide e-seals and S/MIME encryption.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Modernizing Enterprise Credential Management: Zero-Knowledge Architecture &amp; Identity Governance</title>
      <link>https://marcelwiedemeier.com/post/password-manager/</link>
      <pubDate>Sun, 15 Apr 2018 10:00:00 +0200</pubDate>
      <guid>https://marcelwiedemeier.com/post/password-manager/</guid>
      <description>&lt;p&gt;In modern distributed enterprises, compromised credentials remain the single most common initial attack vector in data breaches. Legacy password solutions often suffer from severe structural deficiencies: fragmented local desktop databases, lack of centralized revocation, unmonitored plaintext exports, and widespread sharing of administrative credentials over unencrypted channels.&lt;/p&gt;
&lt;p&gt;When modernizing the password management infrastructure at Unic, our mission was clear: eliminate password reuse and unsecured credential sharing while instituting strict zero-knowledge security and comprehensive audit logging.&lt;/p&gt;
&lt;h2 id=&#34;the-security-challenges-of-legacy-credential-stores&#34;&gt;The Security Challenges of Legacy Credential Stores&lt;/h2&gt;
&lt;p&gt;Our legacy system (Password Manager XP) presented several critical risk vectors:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Lack of Zero-Knowledge Encryption&lt;/strong&gt;: Centralized databases where decryption keys could potentially be intercepted or mishandled during synchronization.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Coarse-Grained Access Control&lt;/strong&gt;: Inability to enforce strict role-based access control (RBAC) across distinct Business Units (BUs) and client delivery teams.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Absence of Real-Time Audit Trails&lt;/strong&gt;: No verifiable logging of who accessed specific client production API keys or administrative root passwords.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Friction-Driven Workarounds&lt;/strong&gt;: Cumbersome UX led engineers and consultants to cache credentials in local text files or unencrypted browser storage.&lt;/li&gt;
&lt;/ol&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;+-----------------------------------------------------------------------------------+
|                        Zero-Knowledge Enterprise Vault                            |
|                                                                                   |
|  +--------------------+     Master Password + Secret Key    +------------------+  |
|  | Client Device /    | ----------------------------------&amp;gt; | Client-Side      |  |
|  | Browser Extension  | &amp;lt;---------------------------------- | AES-256 GCM      |  |
|  +--------------------+      Encrypted Ciphertext Only      +------------------+  |
|            |                                                         |            |
|            v TLS 1.3 Secure Enclave Tunnel                           v            |
|  +--------------------+     Encrypted Vault Storage         +------------------+  |
|  | Cloud Platform /   | ==================================&amp;gt; | Zero-Knowledge   |  |
|  | Identity Provider  |                                     | Encrypted Blobs  |  |
|  +--------------------+                                     +------------------+  |
|            |                                                                      |
|            +--------&amp;gt; Immutable SIEM Audit Logs &amp;amp; Anomaly Detection               |
+-----------------------------------------------------------------------------------+
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;architectural-blueprint--security-safeguards&#34;&gt;Architectural Blueprint &amp;amp; Security Safeguards&lt;/h2&gt;
&lt;p&gt;To address these vulnerabilities, we migrated to a modern cloud-native secrets platform built on zero-knowledge encryption principles:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dual-Key Client-Side Cryptography&lt;/strong&gt;: Every vault item is encrypted and decrypted exclusively on the client endpoint using AES-256 in GCM mode, derived from a combination of the user&amp;rsquo;s master password and a high-entropy 128-bit Account Secret Key. The hosting infrastructure never receives or stores plaintext credentials or master keys.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Vault Segmentation &amp;amp; Principle of Least Privilege&lt;/strong&gt;: Each Business Unit operates within dedicated, cryptographically isolated vaults. Sensitive production infrastructure keys are partitioned from day-to-day application logins.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Separation of Enterprise and Personal Secrets&lt;/strong&gt;: Clear policy segregation ensures that corporate secrets remain auditable and transferable upon employee offboarding, while personal credentials remain private to the user.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Native Browser &amp;amp; CLI Integration&lt;/strong&gt;: By providing seamless autofill with phishing protection (verifying exact domain FQDNs before presenting credentials), we neutralized credential-harvesting phishing campaigns.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automated Audit Logging &amp;amp; SIEM Ingestion&lt;/strong&gt;: Real-time events for credential reads, permission modifications, and unusual geographic logins are continuously streamed into centralized monitoring systems.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;business-unit-clean-up--migration-strategy&#34;&gt;Business Unit Clean-up &amp;amp; Migration Strategy&lt;/h2&gt;
&lt;p&gt;A security tool is only as effective as the data hygiene behind it. We appointed dedicated Security Champions across every Business Unit to conduct structured audits:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Deprecating stale accounts and cycling all shared client production passwords during ingestion.&lt;/li&gt;
&lt;li&gt;Enforcing Mandatory Multi-Factor Authentication (MFA) via FIDO2 WebAuthn hardware security keys.&lt;/li&gt;
&lt;li&gt;Preparing the platform for guest and external contractor access, enforcing time-bound, read-only credential delegation without disclosing underlying master passphrases.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;By prioritizing usability alongside uncompromising cryptographic architecture, we achieved 100% organizational adoption, eliminated unmanaged password repositories, and established a scalable foundation for zero-trust identity management.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
