Security / High-Compliance Delivery
High-Compliance Client-Environment Delivery Model
For organizations with stricter IT controls, regulated environments, or formal compliance requirements, nAblement can deliver the entire engagement inside your environment. Nothing from the engagement exists outside it: everything we build and write stays where it was created, under the controls your organization already runs.
What Stays in Your Environment
Six controls, each one run by your organization
Accounts, code, software, AI, documents, and devices all remain under your control for the whole engagement.
- 01
Accounts issued by your IT
We use named accounts in your identity provider with multi-factor authentication. Access is limited to the systems listed in the statement of work and expires on the agreed date. Shared credentials and long-lived API keys are not used.
- 02
Code stored in your repositories
All code is committed to your version-control organization and built through your development process. Repositories are never cloned or mirrored to nAblement systems.
- 03
Software running in your environment
Everything we build runs in your AWS, Azure, or Google Cloud account, or on your on-premises infrastructure. Our engineers work through a limited role granted by your administrators. Production data is not copied out of your environment.
- 04
AI approved by your organization
AI runs through your cloud account or tools your organization has approved, such as Amazon Bedrock, Google Vertex AI, or Azure OpenAI. The models used are agreed in writing before work begins.
- 05
Documents kept in your systems
Interview notes, workflow documentation, process maps, roadmaps, and build documents are created in your SharePoint or Google Drive. Communication takes place in your Slack or Microsoft Teams.
- 06
Devices managed by your IT
Our engineers work through a virtual desktop or device issued and managed by your organization. Personal devices are not used.
How It Works
Your IT team onboards us the way it would onboard another contractor and offboards us the same way
Onboarding, delivery, and offboarding: when access is granted, how it is used, and how it ends.
- 01
Your IT provisions access
Before work begins, your IT team provides the required accounts, device access, repositories, and cloud environment. The statement of work identifies each system we can access and when that access expires.
- 02
Our engineers work inside your environment
Interviews, workflow mapping, design, development, and testing all happen within the environment your IT team provides. Your organization's access logs record activity throughout the engagement.
- 03
Your IT revokes access
At the end of the engagement, your IT team removes the accounts and permissions it provided, and we confirm in writing that nothing from the engagement remains on nAblement systems.
Discuss your security requirements
Tell us about your IT controls and how an engagement would need to operate within them.