Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  / ,

  / Kertos and Axipro Partner to Streamline Compliance for European Companies

Kertos and Axipro Partner to Streamline Compliance for European Companies

Axipro, the cybersecurity and compliance consulting firm, and Kertos, the European compliance automation platform, and  have entered a strategic partnership that combines software automation with hands-on implementation support for organisations navigating Europe’s expanding regulatory regime.

The agreement, effective April 1, 2026, names Axipro as an implementation partner for Kertos. Customers can now buy the Kertos platform through Axipro alongside consulting, implementation support, and broader compliance service packages spanning frameworks including GDPR, NIS2, DORA, the EU AI Act, ISO 27001, and SOC 2.

The partnership lands as European companies face mounting regulatory pressure. The NIS2 Directive pulled around 28,700 additional companies into scope when it replaced its predecessor in October 2024. DORA became fully applicable in January 2025, binding around 22,000 EU financial entities to a single ICT risk management framework with penalties of up to 2% of global turnover. The EU AI Act adds another layer, with compliance costs for SMEs running between €50,000 and €500,000 per organisation depending on use case.

What the partnership delivers

Under the agreement, Axipro sells, implements, and operates Kertos for customers as part of integrated service packages. The same partner that scopes the gap assessment, defines the control framework, and runs the implementation also configures and operates the platform that holds the evidence. Engagements no longer hand off between separate vendors.

For Kertos, the deal gives the platform deeper exposure to how compliance programmes run inside operating businesses, feeding back into product development. For Axipro, which already supports companies across more than 20 frameworks with services spanning penetration testing, internal audit, and end-to-end certification support, Kertos extends its offering with continuous evidence collection, control management, vendor management, and automated audit preparation.

“Our ambition at Kertos is to build the leading compliance automation platform in the market, one that doesn’t just simplify compliance but fundamentally redefines how companies achieve and maintain it,” said Dr. Kilian Schmidt, CEO of Kertos. “Strategic partnerships like the one with Axipro are a key part of that journey. By working closely with experienced compliance experts, we gain invaluable real-world insights that directly shape and accelerate our product development.”

Free migration to Kertos through Axipro

As part of the partnership, Axipro is offering free migration to Kertos for companies currently using another compliance or GRC platform. The migration covers transferring existing controls, evidence, policies, and vendor records into Kertos, with Axipro consultants handling the rebuild of framework mappings for ISO 27001, SOC 2, GDPR, NIS2, and other applicable standards. The aim is to remove the cost and disruption that typically deters companies from switching platforms mid-program, even when their existing tooling no longer fits their regulatory scope.

 

DACH region as the starting point

Germany consistently leads European GRC adoption and accounts for the largest share of the region’s GRC platform market. It is also where regulatory pressure is sharpest right now, with the Federal Office for Information Security actively building out supervisory capacity ahead of the April 2026 NIS2 registration deadline for essential and important entities.

“Compliance is only as strong as the tools and partners behind it,” said Ali Hayat, CEO of Axipro. “Our partnership with Kertos gives our clients in the DACH region access to a powerful data privacy and compliance platform, backed by Axipro’s hands-on expertise. Together, we make achieving and maintaining compliance seamless, faster, and more predictable for the businesses that need it most.”

Both companies framed the agreement as a foundation for deeper collaboration as customer needs and regulatory requirements continue to evolve.

About Axipro

Axipro is a cybersecurity and compliance consulting firm helping high-growth companies achieve and maintain regulatory certifications across more than 20 frameworks including SOC 2, ISO 27001, GDPR, and NIST. Services span penetration testing, internal audit, and end-to-end support for companies pursuing first-time certification or maintaining existing ones. Axipro has offices in the UK, the USA, and Bahrain.

About Kertos

Kertos is a compliance automation platform that helps companies operating in Europe meet and maintain compliance requirements for frameworks including ISO 27001, SOC 2, GDPR, and NIS2. By automating evidence collection, control management, vendor management, and audit preparation, Kertos enables organisations to build and maintain robust information security and data protection programmes without the manual overhead of traditional approaches.

Read the full press release here

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Axipro Author

Picture of Pedro Dias

Pedro Dias

Pedro has been writing online for over 10 years. With experience in all things programming, cyber security, and compliance, he is our editor-in-chief at Axipro.

Blog Highlights

Explore More Articles

A 300-question security review used to eat a full week of an analyst’s time. In 2026, the teams winning enterprise deals turn that same review around in an afternoon. The gap between those two outcomes is no longer about how many people you throw at the problem. It is about whether your answers live in a structured, searchable knowledge base that AI can draw from, or whether they are scattered across old spreadsheets, Slack threads, and the memory of one overworked security engineer. Security questionnaires have grown longer, more frequent, and more specific. Buyers send the Standardized Information Gathering (SIG) questionnaire, the Consensus Assessments Initiative Questionnaire (CAIQ), the HECVAT for higher education, and an endless stream of custom forms, often through portals like OneTrust or ServiceNow that resist copy-paste. Each one stalls a deal until someone answers it. That is why questionnaire automation has shifted from a nice-to-have to a core part of how revenue and security teams operate. This guide reviews the nine tools worth evaluating this year, maps each to the team it actually fits, and shows you how to choose without falling for the inflated accuracy claims every vendor prints on its homepage. What Is Security Questionnaire Automation Software? Security questionnaire automation software uses AI, usually a large language model (LLM) paired with retrieval-augmented generation (RAG), to draft answers to incoming vendor security assessments. Instead of an analyst hunting through a SOC 2 report or a policy document, the software matches each question to verified content in a central knowledge base and generates a cited response in seconds. The better platforms do more than draft text. They ingest a questionnaire in any format, route questions that need a human to the right subject matter expert, attach supporting evidence, track approvals, and submit the finished response back in the buyer’s original format or portal. The output is a workflow, not just a wall of generated answers. Key Benefits of Using Security Questionnaire Automation Software Faster Turnaround on Security Reviews Speed is the headline benefit and the one buyers feel first. Teams routinely report cutting response time from several days to a few hours, and concierge services advertise turnaround as short as twelve hours on standard questionnaires. When a security review is the last gate before a contract signs, shaving a week off it directly accelerates the sales cycle. Higher Accuracy and Consistency Manual answers drift. One analyst describes your encryption posture one way, another phrases it differently three months later, and a sharp-eyed buyer notices the inconsistency. A central knowledge base enforces one approved answer per question, so every response reflects the same source of truth. That consistency matters more than raw speed when a regulated buyer is reading closely. Reduced SME and InfoSec Bottlenecks The real constraint in most questionnaire programs is not typing. It is the queue of questions waiting on a subject matter expert who already has a day job. Automation handles the repetitive eighty percent automatically and surfaces only the genuinely novel questions for human input, which frees your InfoSec team to review rather than author. Stronger Audit Trails and Compliance Posture Every credible platform now logs who answered what, when, and from which source. That audit trail is useful for the questionnaire itself, but it also feeds your broader compliance posture. When an auditor asks how you keep customer-facing security claims accurate, a versioned, evidence-linked knowledge base is a far stronger answer than a folder of spreadsheets. Insider Note: Every vendor on this list advertises an accuracy figure, usually 92 to 96 percent. Read the denominator before you believe it. A 95 percent accuracy rate measured against questions the AI chose to answer is very different from 95 percent across an entire real questionnaire including the hard, company-specific ones. The number that matters is how many answers ship without a human rewrite, and only a pilot on your own questionnaires reveals that. What to Look for in the Best Security Questionnaire Automation Software AI Answer Accuracy and Grounded Retrieval The core engine should retrieve from your approved content and ground every answer in it, not generate plausible-sounding text from a general model. Grounded retrieval is what keeps the AI from inventing a control you do not actually have, which is the failure mode that destroys buyer trust instantly. Knowledge Base Management and Governance The knowledge base is the asset, not the AI. Look for version control, expiry dates on answers, owner assignment, and tools to retire stale content and merge duplicates. A platform that makes library maintenance painful will quietly rot, and a rotten library produces confident wrong answers. Support for Any Questionnaire Format (Excel, Word, PDF, Portals) Buyers send questionnaires in whatever format suits them. If the software handles a clean Excel file but chokes on a messy Word table or a scanned PDF, you will fall back to manual work for a meaningful share of your volume. Format coverage is unglamorous and decisive. Portal Auto-Fill (OneTrust, ServiceNow, ProcessUnity) Portal-based questionnaires are where most automation ROI leaks away. A tool that drafts beautiful answers but cannot push them into an OneTrust or ServiceNow GRC portal leaves you copy-pasting field by field. The strongest platforms offer a browser extension that completes portal forms directly. Important: When you scope a tool, ask specifically how it handles the portals your largest buyers use. Many platforms quietly degrade to a sidebar that helps you find content to paste manually rather than truly auto-filling. That distinction can be the difference between a one-hour review and a half-day of clicking. Evidence and Citation Backing In 2026, sophisticated buyers expect answers backed by source links: a policy, a control record, a test result. Citation backing is becoming the baseline for a buyer to trust an automated answer, and it doubles as your internal proof that the answer is defensible. Collaboration and Approval Workflows Questionnaires are cross-functional. Sales owns the deadline, security owns the truth, and legal sometimes owns the wording. The platform should assign sections, track ownership, and

Three Gulf states now run three different data protection regimes. Saudi Arabia’s regulator has already issued dozens of enforcement decisions. Bahrain has had a working statute since 2019, and the UAE has a federal law on the books but is still waiting on the executive regulations that will give it teeth. For any company operating across the region, the practical question is no longer whether these laws apply but how far apart they sit, and where compliance built for one falls short of another. This is a structured comparison of the personal data protection laws in Bahrain, UAE, and Saudi Arabia: what each one demands, where they converge on familiar GDPR principles, and the specific points where treating them as interchangeable will get you fined. The Three Laws at a Glance Bahrain moved first. Law No. 30 of 2018, the Personal Data Protection Law (PDPL), came into force on August 1, 2019, making it the first comprehensive standalone data protection statute in the Gulf Cooperation Council. It is supplemented by ten ministerial resolutions issued in 2022 that cover transfers, security measures, and notification procedures. The UAE followed with Federal Decree-Law No. 45 of 2021, effective January 2, 2022 — the country’s first federally applicable, GDPR-style law, issued alongside Federal Decree-Law No. 44 of 2021, which created the UAE Data Office as the federal regulator. The catch is that the executive regulations meant to flesh out timelines and penalties have still not been published, which leaves parts of the regime in a holding pattern. Saudi Arabia’s Personal Data Protection Law, issued by Royal Decree M/19 in September 2021 and amended in March 2023, is the strictest and the most actively enforced of the three. It came into force on September 14, 2023, and a one-year grace period ended on September 14, 2024. Since then, every organization processing the personal data of people in the Kingdom has been fully on the hook. Worth knowing: Saudi Arabia’s PDPL Saudi Arabia’s PDPL protects a person’s data not only during their lifetime but after death. That post-mortem protection is unusual among global privacy laws and means retention and disclosure decisions cannot assume an individual’s rights simply lapse when they die. Who the Laws Actually Reach All three statutes reach beyond their own borders. Bahrain’s PDPL applies to anyone residing or doing business in Bahrain, and to entities outside the country that process personal data using equipment located inside it. The UAE law applies to the processing of data belonging to people in the UAE, regardless of where the controller or processor is based. Saudi Arabia goes furthest, applying to any entity inside or outside the Kingdom that processes the personal data of Saudi residents — a scope that pulls in international businesses that may never have considered themselves subject to Gulf regulation. The big structural difference is the UAE’s free zones. The federal PDPL does not apply inside zones that maintain their own data protection regimes, most notably the Dubai International Finance Centre (DIFC) and the Abu Dhabi Global Market (ADGM), each of which runs its own established framework. A company in the DIFC answers to DIFC rules, not the federal law. That carve-out has no equivalent in Bahrain or Saudi Arabia, and it matters enormously for regional structuring decisions. Ready for GCC data privacy compliance? Talk to our experts and simplify Bahrain, UAE, and Saudi data privacy compliance. Schedule The Regulators Each country has its own supervisory authority, and they are at very different stages of maturity. Bahrain’s Personal Data Protection Authority (PDPA) operates under the Ministry of Justice, Islamic Affairs and Waqf and has full investigation, audit, and penalty powers. SDAIA — the Saudi Data and Artificial Intelligence Authority — is the current regulator in Saudi Arabia, with long-term supervision potentially moving to the National Data Management Office under the Kingdom’s wider data governance framework. SDAIA is visibly active: its enforcement committees issued 48 decisions confirming PDPL violations across the 2025 and 2026 review cycles, a level of regulatory output that should get the attention of any compliance team operating in the region. The UAE is the outlier. The UAE Data Office exists in law but is not yet fully operational, and the Telecommunications and Digital Government Regulatory Authority was tasked with providing administrative support during the office’s early years. In practice this means data subjects in the UAE currently lack a clear federal route to lodge a complaint, and enforcement guidance is still maturing. That ambiguity cuts both ways: it reduces immediate enforcement risk, but it also makes it harder to know exactly what compliance looks like. Lawful Basis, Consent, and Core Principles Consent sits at the center of all three regimes, but Bahrain leans on it hardest. Bahrain’s PDPL sets a default rule that personal data may not be processed without the data subject’s written and explicit consent, with a narrow set of alternative bases such as contract performance, legal obligation, and vital interests. Saudi Arabia and the UAE both recognize consent alongside other grounds, and Saudi Arabia’s amended law added legitimate interest as a basis — though it cannot be used for sensitive data and controllers are warned against treating consent as a convenient fallback when a more specific ground applies. Beneath the lawful-basis question, the three laws share the principles that anyone familiar with the same GDPR-shaped foundation will recognize: lawfulness, fairness and transparency, purpose limitation, data minimization, accuracy, storage limitation, and security. The vocabulary and structure track the European model closely, and deliberately so. That means a mature GDPR program is a strong starting point, not a finished one — the architecture transfers, but the local rules introduce enough variation to demand dedicated attention.   Data Subject Rights The rights packages are broadly similar across the three jurisdictions, but the enforcement emphasis differs. Individuals in all three countries can access their data, request correction, and object to certain processing. Saudi Arabia’s PDPL spells out the most comprehensive set — including access, correction, deletion, objection, and portability —

ISO 14001:2026 took effect on April 15, 2026, and it carries the first genuinely new clause the environmental standard has seen in over a decade. Any checklist built against the 2015 edition is now partly out of date. The structure auditors examine has shifted to the ISO Harmonized Structure, climate change is written into the requirements rather than bolted on through an amendment, and a new change management clause gives certification bodies a fresh place to record findings. This guide breaks down what an ISO 14001 certification audit checklist needs to cover now, clause by clause, and how to use it without turning your environmental management system into a paperwork exercise. What Is an ISO 14001 Audit Checklist? An ISO 14001 audit checklist is a structured set of questions and verification points an auditor works through to confirm an environmental management system (EMS) meets the requirements of the standard. It maps each clause to specific evidence: documents, records, interviews, and observed practice. The checklist is the auditor’s working tool, not the audit itself. A good checklist prompts the auditor to look for objective evidence rather than tick boxes, and it leaves room to record where the documented system and actual practice diverge. That gap — between what the procedure says and what people actually do — is where most findings come from. Stay Ahead of ISO 14001:2026 Changes Book an ISO 14001 Gap Assessment Schedule Why You Need an ISO 14001 Audit Checklist Without a checklist, audits drift. Auditors skip clauses, linger on the areas they find interesting, and produce findings that are hard to compare year over year. A checklist enforces coverage and consistency, which matters most when more than one auditor works the program or when you want surveillance results that trend cleanly against the baseline. It also protects you before the certification body arrives. A disciplined internal audit run against a checklist that mirrors the external audit surfaces the same nonconformities your registrar would — while you still have time to fix them. The checklist turns a once-a-year scramble into a repeatable process. Worth knowing: ISO 19011 ISO 19011 is the international guideline for auditing management systems, and it is not a standard you can certify against. You cannot become “ISO 19011 certified.” It exists to make your audit program competent and consistent — which is exactly what a third-party auditor checks when they review your internal audit records. Types of ISO 14001 Audits Not every audit serves the same purpose, and your checklist depth should match the audit type. The four you will encounter are internal, second-party, third-party certification, and the surveillance and recertification audits that follow. Internal Audit Sometimes called a first-party audit, this is conducted by or on behalf of the organization itself. It is a requirement of Clause 9.2, and it is the single most important audit you run, because it is the one you control. Internal audits should be planned across a program, cover the full EMS over the cycle, and use auditors who are competent and independent of the work they assess. Second-Party Audit A second-party audit is one organization auditing another it has a relationship with — most often a customer auditing a supplier or a company auditing its contractors. Under the 2026 revision, with its sharper focus on externally provided processes, products, and services, expect more of these as larger buyers push environmental criteria down their supply chains. Third-Party Certification Audit This is the audit that earns the certificate. An accredited certification body assesses your EMS against ISO 14001 in two stages. Stage 1 is a readiness review that checks whether the system exists, is documented, and is ready to be assessed. Stage 2 verifies that the EMS is fully implemented, effective, and producing the results it claims. Certification follows only once any major nonconformities are closed. Surveillance and Recertification Audits ISO management system certificates run on a three-year cycle governed by ISO/IEC 17021-1. After initial certification, the body conducts annual surveillance audits in years two and three to confirm the system is still operating, then a recertification audit before the certificate expires. Surveillance audits are narrower than the full assessment, but they are not a formality — and many organizations will fold their move to ISO 14001:2026 into a surveillance or recertification visit to keep cost and disruption down. ISO 14001 Audit Checklist: Clause-by-Clause Breakdown ISO 14001:2026 follows the ISO Harmonized Structure, the common framework shared with ISO 9001, ISO 45001, and ISO/IEC 27001. The familiar Plan-Do-Check-Act cycle still runs underneath it. Clauses 1 through 3 cover scope, references, and terms. The auditable requirements live in Clauses 4 through 10, and that is where your checklist does its work. Clause 4: Context of the Organization Verify that internal and external issues, interested parties, and the EMS scope are identified and documented. This is where the 2026 revision lands hardest. Context analysis must now explicitly weigh environmental conditions — including climate change, biodiversity, pollution levels, and the availability of natural resources. A context review that mentions only commercial and regulatory factors will draw a finding. Clause 5: Leadership and Commitment Check for evidence that top management is involved in substance, not ceremony. The environmental policy must be documented, communicated, and appropriate to the organization. Auditors look for real engagement: leaders who can speak to the policy, the objectives, and how environmental performance feeds into business decisions. The 2026 wording tightens leadership accountability, so a policy signed once and forgotten will not hold up. Clause 6: Planning and Risk Assessment This clause covers environmental aspects and impacts, compliance obligations, risks and opportunities, and objectives. It generates more nonconformities than almost any other. The life cycle perspective in Clause 6.1.2 is strengthened, with clearer expectations on upstream and downstream impacts. The headline change is Clause 6.3, Planning of Changes — the only entirely new clause in the revision. It requires a structured, planned approach to changes that affect the EMS, such as new products, site relocations, supplier changes, or process