Services · Supporting service
DevSecOps & CI/CD Security
Security built into your pipelines and infrastructure code, not added after release.
- State
- Available
- Pricing
- Fixed price after scoping
Fit
Who it is for, and when
Who it is for
Teams shipping through CI/CD who want security built in rather than added later.
When to use it
- Pipelines deploy to production without security checks
- Infrastructure code is growing
Services · what our people do
What we do
We add security checks and safer defaults to your pipelines and infrastructure code.
Scope
- CI/CD pipelines
- Infrastructure as code
- Secrets handling
- Secure deployment
Working together
What we need, and what you receive
What we need from you
- Access to the pipelines and infrastructure code in scope
- The engineers who own those pipelines
What you receive
- Pipeline and infrastructure-code changes
- Guidance for your engineers
Boundaries
What this service does not include
- This is engineering work in your own pipelines and code, not a Tricognita tool.
- It is not an ARIA workflow.
ARIA
ARIA and this service
Engineering-led work; ARIA is not part of this workflow.
Coverage
Clouds and pricing
Clouds
- AWS
- Available
- Microsoft Azure
- Available
- Google Cloud
- Not covered
Pricing
Fixed price after scoping
Every engagement is scoped and priced in writing before work starts.
How pricing worksTalk to us about DevSecOps & CI/CD Security.
Tell us about your environment and what you need. You receive a written scope before any work starts.