Ziwo Upgrades to ISO/IEC 27001:2022 with Axipro

Product

SOC 2 Type I & II

Industry

Cloud Communications / Contact Center Software

Company size

51 – 200 employees

Location

Dubai, UAE

Ziwo-ISO-27001-Axipro

Share This Post

Introduction

Compliance is not a checkbox. It is a journey. For Ziwo, that journey meant moving beyond their ISO 27001:2013 certification and preparing for the future. They sought to modernize their security practices, reduce manual work, and align with updated international standards.

With Axipro providing advisory guidance, Drata powering automation, and Insight Assurance serving as the audit partner, Ziwo successfully transitioned its compliance program to meet ISO 27001:2022 requirements.

The outcome was a smooth certification process, completed without non-conformities, and a stronger foundation of trust with customers across the Middle East and beyond.

About Ziwo

Ziwo is a leading cloud-native call center and customer experience (CX) platform. Headquartered in Dubai, with offices in Riyadh, Cairo, and Casablanca, Ziwo supports businesses across the MENA region and beyond.

Their platform helps organizations deliver secure, intuitive, and multilingual customer interactions. Industries served include:

  • BPO and customer support
  • Retail and e-commerce
  • Finance and real estate
  • Travel and hospitality

As a trusted provider, Ziwo already held ISO 27001:2013 certification. As a trusted provider, Ziwo already held ISO 27001:2013 certification. But to keep pace with growth and evolving expectations, they chose to pursue ISO 27001:2022 compliance with advisory support from Axipro, while leveraging Drata for automation and working with Insight Assurance as their audit partner.

Challenge: Scaling & Upgrading Compliance

Ziwo’s leadership recognized that while ISO 27001:2013 kept them secure, it also came with challenges:

  • Manual compliance tracking created inefficiencies.
  • Evidence collection for audits consumed valuable time.
  • Processes were fragmented across teams.
  • New ISO 27001:2022 requirements required updated alignment.

The goal was clear: transition smoothly to ISO 27001:2022, reduce administrative overhead, and empower their internal team to manage compliance more effectively. This meant choosing the right advisory, automation, and audit partners to guide the process.

Solution: Axipro’s Guided Transition

Through this coordinated effort, Ziwo:

  • Successfully upgraded from ISO 27001:2013 to ISO 27001:2022 certification.
  • Completed the certification with zero major or minor non-conformities, as confirmed by Insight Assurance.
  • Integrated Drata for continuous, automated compliance monitoring.
  • Strengthened their internal team’s ability to manage compliance independently going forward.

This achievement highlights Ziwo’s commitment to security and governance while also showcasing the value of advisory, automation, and audit working together.

“Thanks a ton for the smooth audit, team! It was a combined effort and great teamwork. We look forward to continuing this success in upcoming audits and certifications on behalf of Ziwo & management.” — Ziwo Management

Results: Smooth Audit, Stronger Governance

The partnership delivered results that mattered. With Axipro’s support and Drata’s automation, Ziwo achieved:

  • ISO 27001:2022 certification with zero major or minor non-conformities.
  • Full Drata integration, giving real-time visibility into compliance status.
  • Audit preparation that shifted from manual to automated, saving weeks of effort.
  • An empowered internal team, now confident in managing and scaling compliance.

This wasn’t just an upgrade, it was a transformation. Ziwo replaced administrative burden with operational efficiency. They gained trust, credibility, and a stronger security posture that customers value.

Thanks a ton for the smooth audit, team! It was a combined effort and great teamwork. We look forward to continuing this success in upcoming audits and certifications on behalf of Ziwo & management. — Ziwo Management

Ready to see the same results? Modernize your audits today with ISO 27001:2022 compliance with Axipro.

Why Ziwo Chose Axipro

For Ziwo, selecting Axipro as an advisory partner was driven by the need for clarity and structure during the transition. They valued Axipro’s ability to:

  • Provide guidance on aligning with ISO 27001:2022 requirements.
  • Support the adoption of automation tools like Drata.
  • Collaborate with internal teams rather than replace them.
  • Partner effectively alongside Insight Assurance as the independent auditor.

Axipro’s role was not to certify or audit, but to act as a trusted advisor, helping Ziwo navigate the complexity of compliance and build confidence in their processes.

Conclusion

Compliance is not a one-time milestone. It evolves as standards change and organizations grow. Ziwo’s successful transition from ISO 27001:2013 to ISO 27001:2022 certification demonstrates the value of combining advisory guidance, automation, and independent auditing.

With Axipro as their advisory partner, Drata providing automation, and Insight Assurance serving as the audit partner, Ziwo strengthened its compliance program while ensuring alignment with international best practices. The result was a smooth certification process, completed with zero non-conformities, and an internal team better prepared to manage compliance moving forward.

For organizations looking to upgrade or begin their compliance journey, Axipro provides advisory support to help teams align with updated standards, adopt automation tools, and prepare confidently for audits.

Fractional CISO Cost in 2026: What You’ll Pay, From $500 to $25,000 a Month

A fractional CISO costs anywhere from $500 to $25,000 a month in 2026. This range might look absurd until you analyze what’s included at each level of spending, and that’s exactly what we’ll do in this article. At $500 you’re buying a compliance-led security program with a virtual CISO attached, run by a team that already knows SOC 2 and ISO 27001 well. At $25,000 you’re buying two or three days a week of a senior executive’s time and team, to run security for a company with real headcount and a board that asks hard questions. Both make sense for the right company. Buy the wrong one and you either overspend by six figures or end up short on leadership right before a breach or a failed audit. This guide covers fractional CISO pricing by model, tier, company stage and framework, compares it with the full cost of a full-time hire, and shows where Axipro’s published price of $500 per month fits. TL;DR: Fractional CISO Cost at a Glance Engagement type Typical 2026 cost Best fit Early-stage Startup compliance vCISO (Axipro Trust Assurance Plan) $500 to $850 per month, certification billed separately Startups and SaaS teams that need SOC 2 or ISO 27001 kept running, with a dedicated vCISO Advisory retainer (1 to 2 days per month) $3,000 to $6,000 per month Teams with a capable IT lead who need executive direction Operational retainer (4 to 6 days per month) $8,000 to $16,000 per month Growth-stage companies running several frameworks Embedded retainer (close to half-time) $15,000 to $25,000+ per month Mid-market and regulated organizations Hourly advisory $200 to $500 per hour One-off questions, incident support Fixed-fee project $4,000 to $75,000 per project Gap assessments, roadmaps, certification Full-time CISO (total compensation) $250,000 to $700,000+ per year Large or heavily regulated companies with a security team to lead Most companies under a few hundred employees don’t need a full-time Chief Information Security Officer (CISO). They need one person who’s accountable for security, audits and customer questionnaires. A fractional or virtual CISO (vCISO) fills that role. What you pay mostly comes down to two things: how many hours of senior time you buy, and how much of the hands-on work is included. Average Fractional CISO Cost Breakdown People use fractional CISO and vCISO interchangeably. Both mean a part-time security executive who owns strategy, risk and compliance without joining your payroll, so the pricing below applies to both. Monthly Retainer Pricing Ranges Retainers are the standard way to buy fractional security leadership. Most providers price them by days of senior time per month, and 2026 rate cards fall into three bands. Advisory retainers of one to two days a month run $3,000 to $6,000. Operational retainers of four to six days run $8,000 to $16,000. Embedded retainers, close to half-time, run $15,000 to $25,000 or more. There’s now a fourth band below all three. Early-stage vCISO plans pair a virtual CISO with a GRC team, continuous compliance monitoring, and audit preparation for a flat monthly fee. Axipro’s Trust Assurance Plan costs $500 a month for one framework (ISO 27001 or SOC 2) and $650 a month for the ISO 27001 + SOC 2 bundle, and you can cancel anytime. The monthly fee covers keeping your program running after certification. Getting certified is a separate fixed fee through Axipro’s Achievement Plan. The pricing works because the scope is fixed, and the vCISO team does most of the work instead of billing by the hour. Hourly Rate Pricing Hourly rates for fractional CISOs run $200 to $400 for general advisory work in 2026. Senior operators and incident command go up to $500 an hour. Day rates usually sit between $1,200 and $2,500. Hourly billing suits narrow jobs, like reviewing one security questionnaire or getting a second opinion before a board meeting. It’s a poor fit for building or running a program. Nobody owns the outcome, and the meter runs every time your team asks a question. Project-Based Pricing Fixed-fee projects cover a defined deliverable: a risk assessment, a gap analysis, a security roadmap, an incident response plan or certification. Traditional consultancies charge $25,000 to $75,000 for these, depending on scope. Startup-focused providers charge far less. Axipro’s Achievement Plan covers full SOC 2 or ISO 27001 implementation, from gap analysis to certification audit, for a fixed $4,000 for companies under 50 employees and $5,500 for larger ones, with certification guaranteed. For a lot of startups, that one project is most of what they’d have hired a fractional CISO to do in year one. Annual Cost Expectations Here’s what the bands add up to over a year: Engagement Annual cost Axipro Trust Assurance Plan (single framework) $6,000 Axipro Trust Assurance Plan (ISO 27001 + SOC 2) $7,800 Advisory retainer $36,000 to $72,000 Operational retainer $96,000 to $192,000 Embedded retainer $180,000 to $300,000+ Budget separately for costs that rarely sit inside a retainer: the external audit fee paid to your CPA firm or certification body, penetration testing and security tools. On Axipro, certification is also separate. It comes through the Achievement Plan’s one-off fixed fee. What You Get at Each Price Point Entry-Level: $6,000 to $40,000 Per Year Productized, compliance-led vCISO services sit in this tier. At $500 a month, Axipro’s Trust Assurance Plan includes a dedicated vCISO, continuous compliance monitoring, updates when regulations and standards change, and preparation for your annual surveillance audit. It also covers policy and documentation upkeep, GRC platform integration and management, post-incident analysis, security awareness campaigns, post-certification metric reporting, and 24/7/365 SOC monitoring with SIEM-based threat detection and alerting. Getting certified in the first place is a separate fixed fee through the Achievement Plan. This tier is built for SaaS and tech companies whose need for security leadership comes from SOC 2 compliance, ISO 27001, customer security questionnaires and enterprise procurement reviews. It isn’t built to give you a named executive who spends two days a week inside your company, manages a team of security engineers and presents to a public-company audit committee.

Read More »

php2shell Compliance Checklist: What SOC 2, ISO 27001, HIPAA, PCI DSS and GDPR Require You to Do About CVE-2026-109618 and CVE-2026-109619

Every PHP installation that serves web requests has been open to unauthenticated remote code execution since 2004. On October 21, 2026, the PHP project shipped the fix, the NSA told organizations to take unpatchable systems offline, and four European governments pulled their own websites to patch. Your security team is handling the interpreter. This article is for the person who has to explain the response to an auditor. php2shell is a security incident, and it’s also a live test of the vulnerability management, asset inventory, incident response and vendor management controls you attested to in your last audit. Every framework Axipro works with has a specific expectation for what you do in the next 72 hours and what evidence you keep. Below is the mapping, framework by framework: the control reference, what you need to do, and the artifact that satisfies it. What php2shell Is, in One Minute Two flaws in PHP core, CVE-2026-109618 and CVE-2026-109619, both rated 9.2 on CVSS v4.0, let an unauthenticated attacker run code on the server. The first is triggered through out-of-memory handling that interrupts PHP while request data is only partially initialized. The second exploits request-owned internal state that survives after its memory has been freed. According to the CISA alert, the flaws affect every PHP installation serving web requests, including PHP-FPM, Apache with mod_php, and embedded deployments. The fixes are in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and earlier are end-of-life and get no official fix. Some Linux distributions and long-term support vendors are backporting patches, but the PHP project itself won’t. CERT-EU’s advisory notes that technical details are public and proofs of concept are circulating, so expect exploitation attempts now rather than later. The discovery story matters for one section of this article. Researchers at Calif, working with OpenAI, reported the first flaw on August 11. Wiz reported the second on August 24. Both used frontier AI models to find bugs that had survived two decades of human review, and Wiz warned that the same models can now adapt an exploit across PHP versions, configurations and memory layouts. That changes the threat model your AI governance documentation describes. We come back to it below. The Six Actions Every Framework Expects The frameworks differ in control numbering and in how fast they want you to move, but they converge on the same six steps. Each step produces one artifact. If you do nothing else, produce these six and attach them to the controls listed in the mapping section. Detect and log. Record when you became aware of the advisory, from which source, and who triaged it. A ticket with a timestamp is the minimum. If nobody logged the advisory, your continuous monitoring control is a sentence in a policy rather than something that operates. Scope the exposure. Query your asset inventory for every host running PHP and record the version on each. That includes the marketing website, staging and QA environments, internal tools, customer portals and anything a contractor stood up two years ago. Every PHP installation serving web requests is in scope, not only the ones inside your SOC 2 system boundary. Patch and restart. Update to the fixed version for your branch, then restart PHP-FPM or the web server. The old interpreter stays loaded in memory until the process restarts, so a package update without a restart leaves the host vulnerable. Capture the version output before and after, plus the restart log. Decide on end-of-life hosts, in writing. Anything on PHP 8.1 or older gets one of three outcomes: upgraded to a supported branch, taken offline, or formally risk-accepted by someone with the authority to accept it. CISA’s guidance is to take unpatchable systems offline. If you choose otherwise, the risk register entry needs an owner, a compensating control and a review date. Verify what your vendors did for you. Managed hosts and PaaS providers patched fleet-wide, but under the shared responsibility model you still own the verification. Collect the vendor’s status notice and run your own version check against the live host. Close the loop. Write a short post-incident note covering when you learned, when you patched, what was out of scope, what broke and what changed. This one document is the difference between a scramble and audit evidence. Important: A patch isn’t applied until the process restarts. We’ve seen the same pattern during this disclosure window: apt upgrade runs, the package manager reports the new version, php -v on the command line confirms it, and the long-running PHP-FPM workers serving traffic are still the old binary. Verify with the running process, not the installed package. Framework-by-Framework Mapping SOC 2 (AICPA Trust Services Criteria) SOC 2 doesn’t prescribe a patch deadline. It asks whether your controls operated as designed during the period, and php2shell lands squarely inside the Common Criteria your auditor tests every year. CC7.1 requires detection and monitoring procedures to identify susceptibilities to newly discovered vulnerabilities. Evidence: the advisory in your ticketing or GRC platform with a timestamp, and your vulnerability scanner’s detection of the affected version on each host. CC3.2 and CC3.4 cover risk identification and the analysis of significant changes. Evidence: a risk register entry for php2shell with likelihood, impact and treatment, plus a note on any host where treatment deviates from the standard patch. CC7.3 and CC7.4 cover the evaluation of security events and the response to incidents. Even without confirmed exploitation, php2shell meets the threshold for a security event that has to be assessed. Evidence: the triage record, the decision on whether to invoke the incident response plan, and the remediation ticket trail. CC8.1 governs change management. Emergency patches are still changes. Evidence: the change record for each patch, with approval, testing notes (or the documented decision to skip pre-production testing under emergency change procedures), and a rollback plan. CC9.2 addresses vendor and business partner risk. Evidence: the hosting provider’s status notice and your own verification output. If the Availability category is in scope, taking systems offline to patch triggers A1.2

Read More »