DevSecOps Pipeline Guide: Automating Security Checks
A practical DevSecOps guide for product teams: which security checks to automate in CI/CD, how to avoid alert fatigue and what to ask an outsourced team.
Learn how SLIs, SLOs and error budgets turn vague uptime promises into clear targets, and how to agree them with an outsourced development team.
“The app must be available all the time” is one of the most common requirements in a software contract, and one of the least useful. It cannot be measured, it cannot be costed, and it gives the team no way to decide between shipping a feature and fixing a reliability problem.
Service level objectives (SLOs) and error budgets replace that sentence with something concrete. They give founders, product managers and engineers a shared language for how reliable a service needs to be, and what to do when it falls short.
The error budget is simply what is left after the SLO: if the target is 99.9% over 30 days, the remaining 0.1% of that period is the amount of failure you can tolerate. A 99.9% target over 30 days allows roughly 43 minutes of full unavailability.
Without a budget, reliability and speed of delivery are argued about on opinion. With one, the rule is simple:
This removes the blame from the discussion. Nobody is “too cautious” or “too reckless”; the data decides.
Measure what users actually experience, not what servers report. A server can be healthy while the login page fails.
| User journey | Useful SLI |
|---|---|
| Browsing or API reads | Percentage of requests returning a non-error response |
| Checkout or payment | Percentage of attempts that complete successfully |
| Search or dashboards | Percentage of requests faster than an agreed threshold |
| Background processing | Percentage of jobs finished within the agreed window |
| Mobile app launch | Percentage of sessions that start without a crash |
Pick two to four SLIs for the journeys that matter most to revenue or retention. More than that and nobody will look at them.
Higher targets cost disproportionately more. Moving from 99% to 99.9% typically needs better monitoring, automated rollbacks and redundancy; going further often needs multi-region design and a larger on-call commitment.
A practical approach:
Not every feature needs the same target. A payments flow and an internal reporting page deserve different objectives.
SLOs are especially valuable when development and operations are split across companies or time zones, because they replace subjective status reports with numbers both sides trust.
If you want reliability targets defined, monitored and enforced across your product, our cloud and DevOps services cover monitoring, alerting and release automation, and our support and maintenance teams run live applications against agreed objectives. To discuss your own setup, contact us.
A practical DevSecOps guide for product teams: which security checks to automate in CI/CD, how to avoid alert fatigue and what to ask an outsourced team.
How to design a staging environment that catches real bugs before release: parity, data, cost control and preview environments for outsourced teams.
How to store API keys, passwords and certificates safely in cloud apps, what to avoid, and what to demand from an outsourced DevOps team.
Tell us about your platform, your product idea or the systems you want to modernise. Someone from our Chennai engineering team will get back to you personally.