Abstract
Safer Alternatives to Shared Executive Credentials addresses how assistants can act for executives without sharing reusable credentials. The source record supports a bounded conclusion: identity guidance favors individual authentication and strong factors because shared secrets weaken attribution and revocation. [2] [3] [9] [10] The practical proposal is to prefer native delegation, named role access, phishing resistant authentication, managed vault release, and audited break glass procedures. This brief treats that proposal as a testable local control, not a guaranteed productivity, security, staffing, or health outcome.
Methodology
Editors screened the 13 linked sources as a cluster bibliography for authority, traceability, and potential relevance. Only citations attached to an evidence sentence are represented as direct support for that claim; uncited bibliography entries provide broader context and are not claimed to support every statement. Empirical studies were distinguished from occupational descriptions, public guidance, and normative standards. No new statistic was calculated by combining unlike studies. Recommendations below are labeled as operating practices and remain subject to the stated limitations.
Decision boundary for how assistants can act for executives without sharing reusable credentials
Native delegation preserves individual identity. Named role accounts, controlled vault release, and emergency access address different legacy constraints and need distinct logging and recovery. This boundary prevents unlike activities from being counted as equivalent and identifies where human judgment must remain visible. Records should describe the work without copying confidential content that is unnecessary for the decision.
What the evidence can support
Identity guidance favors individual authentication and strong factors because shared secrets weaken attribution and revocation. [2] [3] [9] [10] The sources differ in population, purpose, and method, so they do not establish one universal target. Their useful contribution is a set of observable conditions and controls that a team can test in its own operating environment.
Operating risks in safer alternatives to shared executive credentials
A vault can centralize a shared secret without restoring attribution. Recovery may depend on a lost phone, and automated integrations can fail after rotation. These failure modes require explicit exception handling and a rollback path. A change that shifts delay, exposure, preparation, or after hours work to another person has not demonstrated a clean improvement.
Proposed local practice
The proposed practice is to prefer native delegation, named role access, phishing resistant authentication, managed vault release, and audited break glass procedures. Implementation should rank shared credentials by consequence, replace high risk cases first, and verify that recovery does not depend on one person. Name the owner, affected roles, information boundary, review date, and condition for stopping before the trial begins. Recurring exceptions should be reviewed as evidence that the rule or surrounding system needs revision.
Measurement and review decision
Relevant measures are shared credential count, strong authentication coverage, failed recovery tests, and unattributed actions. Each indicator needs a written definition and a reliable system of record. Volume should be paired with quality, continuity, or control evidence rather than merged into a synthetic score. At review, the valid choices are keep, revise, narrow, pause, or stop, with the reason recorded.
Limitations and responsible use
The central limitation is that some legacy services lack delegation and require compensating controls until replacement is feasible. Sector, seniority, regulation, technology, time zone, and available backup can alter applicability. This brief is not individualized legal, medical, employment, privacy, or security advice. Consequential changes involving protected information, health concerns, contractual authority, or active incidents require qualified review.
Key findings
- Identity guidance favors individual authentication and strong factors because shared secrets weaken attribution and revocation.
- Native delegation preserves individual identity. Named role accounts, controlled vault release, and emergency access address different legacy constraints and need distinct logging and recovery.
- A bounded practice is to prefer native delegation, named role access, phishing resistant authentication, managed vault release, and audited break glass procedures.
- Review shared credential count, strong authentication coverage, failed recovery tests, and unattributed actions.
- Keep this limitation visible: some legacy services lack delegation and require compensating controls until replacement is feasible.
Sources
- Security and Privacy Controls for Information Systems, NIST
- Zero Trust Architecture, NIST
- Digital Identity Guidelines, NIST
- Privacy Framework, NIST
- Protecting Personal Information, Federal Trade Commission
- Logging Made Easy, UK National Cyber Security Centre
- CIS Controls Version 8, Center for Internet Security
- OWASP Logging Cheat Sheet, OWASP
- OWASP Authentication Cheat Sheet, OWASP
- Digital Identity Guidelines: Authentication and Lifecycle Management, NIST
- Guide to Computer Security Log Management, NIST
- Cybersecurity Framework, NIST
- Computer Security Incident Handling Guide, NIST