Sold by: Millabs Corporation
Your application re-deployed against the hardened baseline on every release, with a findings delta returned in two business days so regressions surface early.
Overview
Remediation is not a milestone you pass once. A base image update, a new dependency, or a routine release can reintroduce exactly what you spent three months removing, and you will find out at admission control if nobody is checking.
What the service does
- Re-deployment on every release you nominate: against a hardened Kubernetes baseline, using the same platform behavior your target enclave enforces.
- A findings delta within two business days: what is new, what is resolved, and what changed severity since the last run. The delta is the deliverable, not another full report to read.
- Regression detection on what quietly comes back: a base image drifting to a vulnerable version, a container that starts running as root again, a new dependency pulling from a blocked registry, a manifest change that breaks admission.
- Re-baselining when the platform moves: hardened platforms tighten their policies over time, and a system that passed last quarter is not guaranteed to pass this one.
Why this matters between now and authorization
The period between "remediation finished" and "authorization granted" is where schedules are lost, and the losses come from changes nobody thought were risky. Two business days of warning is the difference between fixing something in your own pipeline and explaining it to an Authorizing Official.
Who this is for
Vendors between remediation and authorization who are still shipping releases and cannot afford to discover a regression at admission control.
Program offices tracking a vendor's readiness who want evidence on each release rather than a status claim.
Related AWS services
This service supports customers deploying containerized applications on Amazon Elastic Kubernetes Service (Amazon EKS), with container images held in Amazon Elastic Container Registry (Amazon ECR), including workloads destined for AWS GovCloud (US) and other regulated US Government environments.
How the work is performed
Testing runs in a Millabs-operated laboratory, which is privately owned and is not a government-authorized environment. No production or government system is touched. Millabs requires access to your container images and deployment manifests for each release tested.
Scope boundary
Millabs identifies application code quality and security findings but does not remediate application source code. This service reports and explains. Remediation is a separate engagement or your own work.
About Millabs
Millabs Corporation has fielded a commercial application at CONTROLLED and TOP SECRET levels and operates a hardened Kubernetes laboratory built for exactly this class of testing.
SBA-certified Service-Disabled Veteran-Owned Small Business, Woodbridge, Virginia. UEI TE1LXFGDZAS7. CAGE 9H4A3.
Highlights
- A findings delta in two business days: what is new, what is resolved, what changed severity. Not another full report, just what moved since the last release.
- Catches the regressions that quietly return - a drifting base image, a container running as root again, a dependency reaching for a blocked registry.
- Re-baselined when the platform tightens its policies, because passing last quarter does not mean passing this one.
Details
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Pricing
Custom pricing options
Pricing is based on your specific requirements and eligibility. To get a custom quote for your needs, request a private offer.
Legal
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Support
Vendor support
- Email: marketplace@millabs.net
- Phone: 571-730-7459
- Hours: 0900-1700 US Eastern, Monday to Friday, excluding US federal holidays
Before purchase: questions about scope, fit, or what the engagement requires from your team are answered by email within one business day. There is no charge for a scoping conversation.
During the engagement: you work directly with the engineer performing the work, not a support queue. Findings are shared as they are produced rather than held for a final report, and a working session is scheduled at the midpoint and at completion.
After delivery: clarification questions on the delivered artifacts are answered at no charge for 30 days.
Not included: this is a professional services engagement, not a software subscription. Millabs does not provide 24/7 support, on-call coverage, or incident response for your application.
For refund inquiries or engagement disputes, contact marketplace@millabs.net .