<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Identity | Marcel Wiedemeier</title>
    <link>https://marcelwiedemeier.com/tags/identity/</link>
      <atom:link href="https://marcelwiedemeier.com/tags/identity/index.xml" rel="self" type="application/rss+xml" />
    <description>Identity</description>
    <generator>Wowchemy (https://wowchemy.com)</generator><language>en-US</language><copyright>© 2023</copyright><lastBuildDate>Sun, 15 Apr 2018 10:00:00 +0200</lastBuildDate>
    <image>
      <url>https://marcelwiedemeier.com/media/icon_hu_99437298ac1eb4c9.png</url>
      <title>Identity</title>
      <link>https://marcelwiedemeier.com/tags/identity/</link>
    </image>
    
    <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>
