Client-owned access
Work should occur in client-controlled accounts with the minimum permissions required for the assigned workflow.
Security starts with a narrow workflow, client-owned accounts, explicit permissions, approved handling rules, and a complete offboarding path.
Work should occur in client-controlled accounts with the minimum permissions required for the assigned workflow.
Every worker should use an individual identity. Shared passwords should not be the operating model.
Credentials should move through an approved password manager, never chat, email, or unmanaged documents.
NDA, confidentiality expectations, allowed tools, and prohibited data handling should be documented before access is granted.
The engagement should state whether local downloads are allowed, where working files live, and when copies are deleted.
Access removal, file return, credential review, and device checks should follow a named closeout checklist.
Continuity should come from documented procedures and an approved access path, not casually sharing a primary specialist’s credentials.
Approved password manager and identity process
DISCUSSDevice management and endpoint requirements
DISCUSSData retention and deletion periods
DISCUSSAllowed AI tools and client-data restrictions
DISCUSSIncident reporting contact and response procedure
DISCUSSSubprocessor list and cross-border data handling
DISCUSSA responsible proposal should identify the systems, access level, source documents, decision owners, and offboarding steps required.