Seven Low-Cost Credential Controls to Support NIS2 Security Efforts

Summary
The article outlines seven risk-based credential controls organizations can use to improve access visibility and produce audit-ready evidence for NIS2, prioritizing privileged and shared accounts, MFA, reviews, and secure credential storage.
Key points
- Prioritize privileged, shared, and service credentials by inventorying them, assigning owners, and establishing review cycles.
- Apply MFA first to exposed applications, remote access, and privileged administration, where credential compromise poses higher risk.
- Record logs, review dates, and exceptions to show that credential controls are operating.
- Rotate shared secrets when someone with access leaves, since removing their personal account does not invalidate a shared password.
- Keep CI/CD tokens and other service credentials in separately managed storage rather than configuration files or personal accounts.
- The article presents Passwork vaults, permissions, and audit logs as ways to support credential governance; these controls do not by themselves establish full NIS2 compliance.
Article Details
- Defense Focus
- Make privileged, shared, and service credentials visible, owned, revocable, and reviewable, with audit-ready evidence.
- Detection Methods
- Review last-access timestamps to identify candidate dormant accounts.
- Review access and permission histories, including after offboarding and credential rotation.
- Maintain an inventory of privileged and shared accounts with named owners and scheduled reviews.
- Data Sources
- Credential vault audit logs and last-access timestamps
- Permission-history records
- Credential and privileged-account inventories
- Defensive Actions
- Inventory privileged and shared credentials, assign owners, and establish a review cycle.
- Disable dormant accounts and remove default vendor passwords before deployment.
- Prioritize MFA for externally exposed applications, remote network access, and privileged administration.
- Rotate credentials after exposure or a role change; pair offboarding with rotation of secrets the departing person could access.
- Move shared secrets out of chat and spreadsheets into a vault with named-user permissions.
- Isolate CI/CD tokens and other pipeline secrets in owned vault entries and rotate them on a schedule.
- Retain logs, review dates, and exception records as evidence that controls operate.
