Cybersecurity
DevSecOps consulting and engineering security
We build security into how your software is designed, built and run, from the checks in your pipeline to the configuration of your Kubernetes clusters and the coding standards your developers follow. Everything we set up is handed to your team to own.
Overview
DevSecOps means building security into the way software is written, tested and released, instead of checking it once at the end. In practice it comes down to a few concrete things: checks in the pipeline that catch problems on every change, a design that does not trust more than it needs to, containers and clusters configured so that one weakness does not open everything, and coding standards that developers can actually follow. Engineering Security is the Cybersecurity service that sets those up and hands them to your team.
Who it suits
This service suits companies that build and ship their own software, whether a product sold to customers or internal systems the business runs on. Common reasons to start are a large customer's security questionnaire asking how code is reviewed and released, an auditor asking for evidence of secure development, a move to containers and Kubernetes, or a security incident that started with a leaked secret or an outdated component.
It suits teams of different sizes. A small team may need a few well-chosen pipeline checks and one page of coding rules; a larger one may need checks across many repositories, hardened clusters in several environments and standards for several languages.
Secure pipelines
The pipeline is the one place every change passes through, which makes it the best place to check for security problems. We add checks at the stages where each one works best: scanning your own code for common weaknesses, checking the open source components it uses against known vulnerabilities, catching passwords and keys committed by mistake, and scanning container images before they are pushed. We work on GitHub Actions, GitLab CI/CD and Azure DevOps.
Each check is introduced in warning mode first, tuned until what it reports is worth acting on, and only then allowed to stop a build. That order matters: a check that blocks releases with false alarms is soon switched off.
Secure architecture review
Some weaknesses cannot be found by scanning code, because they are in the design: a service that trusts every request from inside the network, sensitive data copied to places it does not need to be, or an administrative function reachable from the internet. An architecture review looks at how the application or platform is put together, how users and services prove who they are, and where data flows and is stored. The result is a written report of the weaknesses, ranked, with the change that removes each one.
Container and Kubernetes security
Containers and Kubernetes make software easier to deploy, and they also add settings that are easy to get wrong. We harden container images so they carry only what the application needs and do not run with more privilege than it requires. We harden Kubernetes clusters on Google Kubernetes Engine, Amazon EKS, Azure Kubernetes Service or your own installation, covering access control, network policies between workloads, how secrets are stored and which workloads may run. The CIS Benchmarks for Kubernetes give a recognised measure for each setting, so your team can see what was changed and check it stays that way. Our article on container security best practices sets out the order we fix the most common weaknesses in.
Secure coding standards
Coding standards only help if developers read them and reviewers use them. We write them for the languages and frameworks your team actually uses, based on OWASP guidance, with short examples of what to do and what to avoid. Where a rule can be checked automatically, the pipeline checks it. The standards are walked through with your developers at handover, and they belong to your team, to update as the codebase and the threats change.
Work on new software can include this service from the start. Our Software Development projects can be scoped with it, and finished software can be tested from the outside through Red Teaming & Penetration Testing.
Deliverables
What you get
- Secure pipeline setup
Security checks added to your build and release pipeline on GitHub Actions, GitLab CI/CD or Azure DevOps, covering your own code, the open source components it uses, secrets committed by mistake and the container images you ship.
- Secure architecture review
A review of how an application or platform is designed, covering how users and services authenticate, where sensitive data flows and is stored, and which parts trust each other, with a written report of the weaknesses and how to remove them.
- Container and Kubernetes security
Hardening of your container images and your Kubernetes clusters on Google Kubernetes Engine, Amazon EKS, Azure Kubernetes Service or your own installation, measured against the CIS Benchmarks for Kubernetes.
- Secure coding standards
Coding standards written for the languages and frameworks your team uses, based on OWASP guidance, with examples of what to do and what to avoid, so that reviewers and developers check against the same rules.
- Documentation and handover
A record of every check, setting and standard we put in place, why it is there and how to change it, walked through with the engineers who will own it from then on.
Process
How an engagement runs
- 01
Understand how you build
We look at how your software moves from a developer's machine to production, which tools and platforms it passes through and what security checks exist today, and talk to the engineers who run it.
- 02
Agree the scope and price
We send a written scope that names each deliverable and how it is priced. Reviews are fixed price; pipeline and cluster work is fixed price or time and materials, and you know which before anything starts.
- 03
Review or build
2 to 6 weeks; build 2 to 4 months
A review ends in a written report. Pipeline and cluster work is done alongside your engineers, a stage or a cluster at a time, so releases keep running while the checks are added and tuned.
- 04
Hand over
Your team receives the documentation and a walkthrough of each check, setting and standard. From then on your engineers own them and can change them as the software changes.
- 05
Come back when you need us
New services, new clusters or a new pipeline can be scoped as a project of their own, priced the same way as the first.
Proof
Credentials and partners
Marco Villarruel, Founder & CEO
- CASE
FAQ
Frequently asked questions
How long does it take and how is it priced?
An architecture review takes two to six weeks and is fixed price. Setting up a secure pipeline or hardening Kubernetes clusters usually takes two to four months, priced as a fixed fee or as time and materials. The number of applications, pipelines and clusters sets most of the effort, and the scope names each one before we start.
Will security checks slow down our releases?
They should not, and we set them up so they don't. Fast checks run on every change; slower ones run where they cost the least time, such as before a release rather than on every commit. Each check is tuned before it is allowed to stop a build, so developers see real problems, not noise they learn to ignore.
Do you fix what the checks find, or do our developers?
Your developers fix the code, because they know it and will maintain it. We set up and configure the checks, the pipeline and the clusters ourselves, and we explain each finding so it is clear what to change. If a finding needs a design change, the architecture review gives the reasoning to plan it.
How is this different from a penetration test?
A penetration test looks at finished software from the outside, the way an attacker would, at one point in time. Engineering security works on how the software is built, so fewer weaknesses reach production in the first place, and keeps working on every change after we leave. The two complement each other, and our penetration testing is scoped separately.
Do you work with the CI/CD tools and cloud we already use?
Usually, yes. We work with GitHub Actions, GitLab CI/CD and Azure DevOps, and with Kubernetes on Google Kubernetes Engine, Amazon EKS and Azure Kubernetes Service, as well as clusters you run yourself. We add security to the tools you have rather than replace them, and we don't resell licences. If you use a platform we haven't worked with, we say so when we scope the work.
Do you train our developers on the coding standards?
Every set of standards is walked through with your developers at handover, with examples from your own code, so the people who follow them understand why each rule is there. Structured training for a wider group of employees is our Cybersecurity Training service, scoped separately.
A customer or auditor asks how our software is secured. Does this help?
Yes. The pipeline checks, cluster settings and coding standards are written down, and each one shows what it protects against. That documentation, together with the architecture review report, gives a customer or an auditor a clear answer to how security is built into your software and how it is kept in place.
We have no security in the pipeline today. Where should we start?
For most teams, with an architecture review of the application that matters most, followed by the first pipeline checks for secrets, vulnerable open source components and container images, which find real problems quickly. Cluster hardening and coding standards follow in the order the review recommends.
Related
Related services
Red Teaming & Penetration Testing
Penetration testing services for web apps, APIs, networks, cloud and Active Directory, plus red teaming. Every test ends with a report and a retest.
ExploreSoftware Development
Software development services for web applications, APIs and integrations, and mobile apps, in TypeScript, React, Next.js, Python, Java, .NET or Go.
ExploreThe engagement
- Duration
- 2 to 6 weeks; build work 2 to 4 months
- Pricing
- Quoted for each engagement
Reviews are fixed price. Pipeline and cluster work is fixed price or time and materials, agreed in the scope before work starts.
- OWASP
- CIS Benchmarks
Next step
Tell us how your software is built and shipped
Name the languages, the pipeline and where it runs. We reply within two business days.