Secure Delivery
No customer data offshore, reviewed imports, least-privilege access and a person's sign-off on every release.
At a glance
When data cannot leave your environment, NGT designs delivery around that constraint: build offshore on mock data, review everything that crosses into your zone, give least-privilege access per role, and have a person sign every release.
The offshore team builds and tests on mock or synthetic data; your real data is connected inside your zone.
Source and package review, licence, SBOM and vulnerability checks, then your approval and import.
Gates fail closed, access is per role and environment, and an audit log records who approved what.
Secure AI Delivery: Design Around the Constraint
A delivery pattern from NGT's AI work for regulated enterprises: no production data offshore, and you control every import.
Point at a source to see what it feeds, or at a result to see where it comes from.
Where the Controls Sit
Five layers between an engineer's change and your production data.
- At the boundaryNothing enters your zone without review, an SBOM, scans and your approval.
- In the pipelineSecurity and quality gates on every change; they fail closed.
- On every environmentAccess per role and environment; production only in time-boxed windows.
- In the recordWrite-once logs of who approved what, kept as audit evidence.
- Your secure zoneReal data, self-hosted models
- Security boundaryReview · SBOM · licence · CVE scan
- Pipeline gatesSAST · SCA · image scan · DAST
- Environment accessRBAC per role × environment
- Audit logWrite-once, who approved what
Explore Secure Delivery
3 pages, each a few minutes to read.
Frequently asked questions
What customers ask first.
NGT holds no certifications of its own. Company certifications belong to FPT Software, with scope confirmed per engagement.
NGT brings the practice: project risk management mapped to ISO 27001 Annex A, and controls designed against your industry's frameworks.
Yes. Engineers can work from a secured area or through virtual desktops, and agents can run on self-hosted open-weight models in your zone.
Only where your policy allows, with enterprise-licensed tools and data sharing off. Customer data is masked, and every output is reviewed like any change.
A delivery pattern: build and test offshore on mock or synthetic data; the release crosses into your zone after review, checks and your approval.
ISO 27001, HIPAA/HITRUST, PCI DSS, GDPR, NIST, SOC 2, CIS, OWASP, GxP, MAS TRM and OSPAR: frameworks NGT works to, not certifications it holds.
In a vault, never in code or pipelines, with pre-commit leak checks and access per role and environment.
