Why a baseline matters now
Software supply-chain attacks, leaked secrets and misconfigured cloud services are now among the most common routes to compromise. At the same time, obligations have increased. Since 11 September 2026, manufacturers of products with digital elements sold in the EU must report actively exploited vulnerabilities and severe incidents under the Cyber Resilience Act, with the Act's main obligations applying from 11 December 2027. Customers in regulated sectors also ask for SBOMs, testing evidence and secure development practices in due diligence.
A baseline gives engineering teams a clear, achievable standard and gives leadership a way to measure it.
The code-to-cloud baseline
1. Protect the source and the pipeline
- Single sign-on and MFA for source control, CI/CD and cloud consoles
- Branch protection and mandatory review for production code
- Least-privilege pipeline permissions, with short-lived credentials
- Secrets kept in a vault, never in code, with automated secret scanning
2. Know what you ship
- Software composition analysis for open-source dependencies and licences
- A software bill of materials (SBOM) generated for each release
- Signed builds and verified provenance for release artefacts
3. Check code and configuration early
- Static analysis (SAST) tuned to reduce noise
- Infrastructure-as-code and container image scanning in pull requests
- Policy guardrails that block insecure cloud configurations before deployment
4. Test what is running
- Dynamic testing (DAST) and API testing against staging and production
- Cloud security posture monitoring across all accounts and subscriptions
- Expert-led penetration testing for major releases and high-risk features
5. Prioritise, fix and verify
- Prioritise findings by exploitability and business impact, not severity labels alone
- Route findings to owning teams in their existing tools
- Retest important fixes and measure time from discovery to verified remediation
Be ready to report
For software manufacturers selling into the EU, the CRA reporting clock is short: an early warning within 24 hours of becoming aware of an actively exploited vulnerability or severe incident, a fuller notification within 72 hours, and a final report within 14 days of a fix for exploited vulnerabilities, or within one month for severe incidents. Reports go through ENISA's Single Reporting Platform. Make sure your vulnerability-handling and incident processes can identify reportable events and route them quickly.
Metrics CTOs should track
| Coverage | Share of repositories and services under automated scanning |
|---|---|
| Exposure | Open material findings in internet-facing services |
| Speed | Median time to verified fix, by severity |
| Supply chain | Share of releases with SBOM and signed provenance |
| Recurrence | Vulnerability classes that keep reappearing |
Frameworks such as the NIST Secure Software Development Framework (SP 800-218) and the OWASP Application Security Verification Standard provide detailed control catalogues if you want to go further.
Common mistakes to avoid
- Adding security gates that block releases without giving developers actionable fixes
- Ignoring CI/CD and source-control permissions, which attackers increasingly target
- Generating SBOMs but never using them to respond to new vulnerabilities
- Measuring the number of findings rather than time to verified fix
- Assuming the Cyber Resilience Act only matters from December 2027, when reporting started in September 2026
Frequently asked questions
Does the Cyber Resilience Act apply to SaaS?
The CRA covers products with digital elements made available on the EU market. Pure SaaS is generally outside its scope unless it forms part of a product's remote data processing. Organisations should assess their specific products, using the Commission's published guidance.
What is an SBOM and why does it matter?
A software bill of materials lists the components in a piece of software. It helps you respond quickly when a new vulnerability is announced in a dependency, and customers and regulators increasingly ask for one.
Where should a small engineering team start?
Start with MFA and branch protection on source control, secret scanning, dependency scanning and cloud posture monitoring. These give the largest risk reduction for the least effort.
How does this support ISO 27001 and PCI DSS?
A code-to-cloud baseline provides evidence for ISO 27001 secure development, configuration management and vulnerability management controls, and for PCI DSS requirement 6 on secure systems and software.
The outcome should be a repeatable system where material exposure is found, owned, fixed and verified, without slowing delivery.
SecuriCentrix helps engineering teams adopt a code-to-cloud baseline using Aikido Security, expert triage and targeted penetration testing.
Free readiness checklists
Work through the checks with your team, then talk to us about any gaps.
ISO 27001 Readiness Checklist
25 checks · ISO/IEC 27001:2022
Get the free checklistIreland and South AfricaPCI DSS v4.0.1 Readiness Checklist
21 checks · PCI DSS v4.0.1
Get the free checklistRelated reading
Sources
- European Commission: CRA reporting obligations
- European Commission: Cyber Resilience Act
- NIST SP 800-218: Secure Software Development Framework
- OWASP Application Security Verification Standard
This article is general guidance, not legal advice.
