01Why this matters now
Since 11 September 2026, manufacturers of products with digital elements sold in the EU have had to report actively exploited vulnerabilities and severe security incidents under Article 14 of the Cyber Resilience Act. The Act's wider requirements, including security by design and vulnerability handling throughout a product's life, apply from December 2027.
Key factManufacturers selling in the EU began reporting actively exploited vulnerabilities under Article 14 of the Cyber Resilience Act.
The UK has its own rules. The Product Security and Telecommunications Infrastructure regime has applied to connected consumer products since 29 April 2024, banning default passwords and requiring manufacturers to publish how vulnerabilities can be reported. Article 25 of the UK GDPR already requires data protection by design and by default. Financial services firms in the EU have also been subject to the Digital Operational Resilience Act since 17 January 2025.
For most software teams, these obligations arrive late. Requirements are written by legal or compliance teams in documents engineers rarely see. Security and privacy reviews happen near the end of a project, when changing the architecture is expensive. Releases get blocked, audits find gaps that should have been designed out and products ship with weaknesses that later put users at risk.
AI-assisted development has added pace to all of this. Code is being written faster than ever, which makes it even more important that regulatory and security expectations are part of the process from the beginning.
02Who this is for
- 01Software companies
- 02Connected device manufacturers
- 03Financial services and fintech
- 04In-house digital teams
- 01CTOs
- 02Engineering managers
- 03Product owners
- 04Security architects
- 05Compliance teams
03How Regulativ helps
Designed to bring regulatory and security requirements into the software development lifecycle. It helps teams:
- Identify which regulations and standards apply to a product based on what it does, where it is sold and what data it handles
- Turn those obligations into practical requirements and checks that developers can act on during design and build
- Flag potential control gaps for the team to review before release, rather than after
- Keep a record of how each requirement was met, ready for an audit or customer assurance request
Covers products that include AI components. It records the system's purpose, risk classification and oversight arrangements from development through to deployment.
Explore AI GovernorHelps the organisation behind the software meet the National Cyber Security Centre's baseline security controls, covering areas such as secure configuration, user access and malware protection.
04What this looks like in practice
- ContextA UK company is building a smart home device for sale in Britain and the EU.
- What happenedAt the design stage, SDLC OneIQ identifies obligations under PSTI and the Cyber Resilience Act and turns them into tickets in the team's backlog, including a vulnerability disclosure policy and a plan for security updates.
- ResultTwo of these would previously have surfaced only during pre-launch review, weeks before shipping.
05Societal outcome
People rely on apps, devices and online services for banking, healthcare, work and family life. When those products are built with security and compliance considered from the start, fewer preventable failures reach the people using them.
For technology companies, building it in early costs less and moves faster than fixing problems after launch. Over time, that approach raises the standard across the industry and strengthens public confidence in technology.