Overview
We are excited to announce a powerful new feature in the CodeB Credential Provider V2 that enhances security and auditability in shared-account environments.
With this update, the Credential Provider can now automatically append the NFC card ID to the Office author name whenever a user logs into or unlocks a Windows workstation.
Example:
username (EA35CF34)
This feature is designed for organizations that require strong identity tracking while allowing shared access to Windows accounts — common in manufacturing, laboratories, healthcare, and other high-turnover environments.
The Problem with Shared Accounts
In many operational settings, multiple team members work under the same Windows account for convenience or workflow reasons.
While this simplifies operations, it creates a significant challenge:
- No personal accountability in Office documents, comments, and metadata
- Difficulty meeting compliance requirements such as ISO 27001 and NIS2
- Limited ability to perform accurate audits or investigations
How the New Feature Works
With the latest update:
- User Authenticates via NFC Card
- Supported cards: MIFARE and DESFire
- The card is linked to a specific employee identity using our LinkNFCCard tool.
- Credential Provider Sets the Office Author Name
- On logon or unlock, the Credential Provider automatically updates the Office author profile to include the NFC card’s unique ID in brackets.
- Example:
username (EA35CF34)
- Full Traceability Inside Office Applications
- Any edits, comments, tracked changes, or metadata modifications in Word, Excel, or PowerPoint now show the exact card ID used for authentication.
- Correlate with Windows Event Logs
- The NFC card ID in Office matches the card ID recorded in Windows logon events, enabling audit teams to trace actions to specific individuals with high confidence.
Benefits
✅ Compliance Ready – Meets identity tracking requirements in ISO 27001 (A.9 Access Control) and NIS2 directives.
✅ Audit-Proof – Every action in Office documents can be linked to a unique user token.
✅ Zero User Effort – Works automatically after logon; no manual changes required.
✅ Perfect for Shared-PC Environments – Maintain operational efficiency without sacrificing traceability.
Requirements
- NFC Card Type: MIFARE or DESFire only (HID cards not supported)
- CodeB Systemtray must be installed and running on the workstation
- CodeB Credential Provider V2 with the latest update applied
Availability
This feature is available now for all customers using CodeB Credential Provider V2 with NFC authentication.
Support for other token types (USB, certificates, TOTP, OIDC) is planned for future releases.
Stay Updated
- CodeB GPT Expert – Your AI assistant for all things Credential Provider V2: Try it here
- WhatsApp Updates Channel – Receive announcements directly: Join here
Contact us at 📧 info@codeb.io or 📧 info@aloaha.com for implementation guidance or to update your existing deployment.