Security
Last updated August 31, 2026
Security begins with a clearly defined boundary around systems, data, people, permissions, and delivery.
An engagement-specific security plan
Controls follow the sensitivity of the work and the systems in scope. The approved engagement plan defines the enforceable requirements before production begins.
Least privilege. Access is limited by role, approved system, project need, and defined duration.
Separated workspaces. Customer data, environments, credentials, and evidence remain within the approved engagement boundary.
Accountable access. Responsibilities, escalation paths, review requirements, and offboarding actions are documented before work begins.
Governed across the data lifecycle
Scoping identifies approved repositories, datasets, tools, subprocessors, locations, transfer paths, sensitive fields, and prohibited actions. Production begins only after responsibilities and access are assigned.
Retention, return, deletion, and evidence requirements are defined at the same time. Access is removed when a role or engagement ends, and exceptions require documented approval.
Control areas for technical delivery
Implementation depends on the customer environment and is confirmed during security qualification.
Identity and access. Named accounts, role-based permissions, multi-factor authentication where supported, periodic access review, and prompt revocation.
Data protection. Approved storage and transfer paths, encryption provided by the selected systems, customer separation, and defined retention and deletion.
Operational evidence. Version history, review records, delivery manifests, and available system logs preserve accountability without collecting unrelated data.
Response and continuity. Named escalation contacts, incident-handling expectations, backup or recovery requirements, and notification terms are agreed for the engagement.
Assurance without inflated claims
We provide security documentation, answer qualification questionnaires, identify relevant subprocessors, and agree contractual requirements appropriate to the engagement.
A framework, questionnaire response, or control description is not a certification. Applied Work states an audit, attestation, or certification only after it has been independently awarded and remains current.
Review security early
Share your questionnaire, data-handling standard, or access requirements during scoping. We will identify the systems, responsibilities, and evidence required for a defensible engagement boundary.
security@appliedwork.ai