Security & compliance

Security & compliance

A secure platform is the starting point, not the finish line. Our certified architects design Genesys Cloud CX so your own controls, evidence and governance hold up under scrutiny.

Security and compliance by design A large royal blue shield with a white padlock sits in the centre. Four tiles surround it, each joined to the shield: PCI secure payments shown by a payment card, data protection shown by a database, single sign-on shown by a key, and roles and access shown by a person with a badge. SECURITY & COMPLIANCE PCI payments Data protection Single sign-on Roles & access

In summary

Genesys Cloud security and compliance starts with a platform that holds a broad set of independent certifications and attestations, but a compliant contact centre depends on how that platform is designed and run. QVCCS designs Genesys Cloud CX solutions that use those controls responsibly: the right region for your data, least-privilege roles and divisions, protected recordings and transcripts, sensible retention and a clear audit trail. Specialists from our own bench work with your security, privacy and risk teams, so every control can be evidenced from the first design document to day-to-day operations.

Who works on this

  • Enterprise Solution Architect
  • Solution Architect
  • Senior Business Consultant / Business Analyst
  • IT Systems, Telecoms & SIP Engineer
  • Systems Integration Tester
  • Senior Platform Practice Lead (Genesys Cloud CX)
  • Platform assurance, used wellWe map Genesys Cloud certifications and attestations to your control framework, and show clearly where your own responsibilities begin.
  • Data in the right regionCore and satellite region choices made early, with the residency, latency, recording storage and certification implications of each option understood.
  • Least-privilege access by designRoles, divisions and permissions designed around real job functions, so people see only the queues, data and recordings they need.
  • Evidence your auditors can followAudit, retention and change records designed in, so you can demonstrate who did what, when, and under which policy.
DiagramLayers of a secure Genesys Cloud CX design
  1. Governance & evidence
    • Policies
    • Audit trail
    • Change control
  2. Access & identity
    • SSO
    • Roles
    • Divisions
  3. Data protection
    • Secure flows
    • Retention
    • Recording access
  4. Region & residency
    • Region choice
    • Integrations
    • Data flows
  5. Genesys platform
    • Encryption
    • Certifications
    • Operations

Genesys secures the platform; QVCCS helps you design and govern every layer you control.

01

Why Genesys Cloud security and compliance matter

Genesys Cloud security and compliance is about more than a list of certificates. A contact centre handles some of the most sensitive data an organisation holds: identity details, account information, health conditions, complaints and payment conversations, often captured in recordings and transcripts that last for years. Regulators, customers and boards expect that data to be protected, used lawfully and kept no longer than necessary. When a CX leader can show how the contact centre meets those expectations, procurement moves faster, audits are calmer and new channels or AI capabilities can be adopted with confidence rather than anxiety.

Cloud contact centres operate on a shared responsibility model. Genesys secures and certifies the platform, its infrastructure and its operations. The client remains responsible for how the tenant is configured: who can access what, which data is captured, where integrations send it, how long it is kept and who approves changes. Most compliance gaps sit in that second half. QVCCS closes them by treating security as a requirement from day one: control requirements sit in the Functional & Non-Functional Requirements Specification, are traced through the design to configuration, and are proven by test and evidence rather than assumed.

02

The Genesys Cloud compliance foundation

Genesys lists support for PCI DSS, SOC 1 Type 2, SOC 2 Type 2, ISO 27001:2022, ISO 27017:2015, ISO 27018:2019, CSA CAIQ and C5, with ISO 42001:2023 for its AI management system and HIPAA support in the Americas. Its Trust Center adds further items such as SOC 3, HITRUST, Cyber Essentials Plus and IRAP, alongside alignment to laws including GDPR and DORA. Genesys Cloud is a PCI DSS Level 1 service provider under version 4.0. These are Genesys platform assurances, not QVCCS certifications, and they do not make a deployment compliant on their own; they give your risk assessments, DPIAs and supplier reviews independent evidence to rely on.

For US government workloads, Genesys Cloud CX is FedRAMP authorised at the Class C (formerly Moderate) impact level, effective June 2023, and Genesys supports FedRAMP only in the AWS US East 2 region. Genesys notes that ISO 27001, 27017 and 27018 do not currently cover that region, and that customers there must follow its FedRAMP participant requirements and secure configuration guide. More generally, organisations live in a core region, while satellite regions can carry media and recording storage, and Genesys announced in July 2026 that Genesys Cloud is available on the AWS European Sovereign Cloud for organisations with strict European data-residency requirements. QVCCS weighs these factors against your obligations early and records the decision in the high-level design, before configuration begins.

Genesys certifies the platform; compliance is earned in how you design, configure and govern it – and that is where our certified people do their best work.

QVCCS point of view

03

Designing the controls you own

Access design is where security becomes practical. Our architects model roles around real job functions rather than copying a generic template, and use divisions to separate business units, brands, regions or outsourced partners so that each group sees only its own queues, users, flows and interactions. We pair this with single sign-on and, where appropriate, automated user provisioning, so joiners, movers and leavers are handled through your identity provider. Integration credentials receive the same discipline: dedicated OAuth clients, minimum scopes, documented owners and a clear process for rotation and revocation, all recorded in the interface contracts.

Data protection decisions run through every journey. We use secure call flows to keep sensitive values out of recordings and logs, decide which interactions are recorded and transcribed, and restrict who can play back, export or delete recordings. Retention policies are agreed with your legal and privacy teams and implemented consistently across voice, digital, screen recording and analytics. For integrations and exports, we document exactly which fields leave Genesys Cloud CX, where they go and why. That level of detail makes subject access requests, deletion requests and data protection impact assessments far easier to answer accurately.

AI introduces its own questions. Virtual agents, copilots and analytics process conversation content, so we design which data they can use, how outputs are reviewed and how decisions are explained. Genesys Cloud certification to ISO 42001:2023 gives your AI governance a credible platform foundation; QVCCS helps you build the policies, guardrails and monitoring on top. The same thinking applies to regulated sectors: for healthcare, financial services and public bodies we agree the specific controls in the requirements baseline and design them in, rather than discovering obligations during a late security review.

04

How QVCCS delivers secure designs

Security cannot be bolted on by one specialist, so we muster a team from our own bench and take collective responsibility for the outcome. The Enterprise Solution Architect and a Solution Architect map Genesys Cloud capabilities and certifications against your control framework and own the security and data-protection design. A Senior Business Consultant / Business Analyst captures policies and regulatory obligations as requirements and builds a responsibility matrix showing what Genesys, QVCCS, your partners and your own teams each own – a document auditors commonly ask to see. An IT Systems, Telecoms & SIP Engineer covers network and telephony controls, and the Senior Platform Practice Lead holds design authority.

From there, security requirements flow into the high-level design, the low-level design and every interface contract we write. We build to those designs, test access rules with realistic personas, run negative tests to prove sensitive data is absent from recordings, logs and exports, and assemble the evidence pack your auditors will ask for, each item traced back to the requirement it satisfies. Where we work as the specialist delivery partner behind a global systems integrator, we align with their security governance. The result is a deployment your information-security team has seen designed, tested and evidenced, not one they are asked to accept on trust.

05

Staying compliant as you evolve

Compliance drifts unless someone watches it. New queues, new integrations, new AI features and new staff all change your risk position. QVCCS provides support and maintenance aligned to your Genesys Cloud CX support model, including periodic access reviews, health checks that retention and recording policies still match your rules, and release impact assessments of Genesys Cloud changes against your controls. Changes follow change control with documented approvals, and we keep your as-built documentation and handover pack current, so the next audit starts from an accurate picture rather than a reconstruction of what was built several years ago.

What you get from QVCCS

  • Control mapping from Genesys Cloud assurances to your framework
  • Shared responsibility matrix covering Genesys, partners and your teams
  • Region and data residency recommendation with documented trade-offs
  • Role, division and permission model built around real job functions
  • Recording, transcript and retention design agreed with legal and privacy
  • Persona and leakage test evidence pack ready for audit
  • Ongoing access reviews and release impact assessments, aligned to your support model

Genesys documentation references

Checked against current official documentation, October 2026. Genesys releases weekly, so we re-validate every design against the live release notes.

  1. Supported security, privacy, and AI standardshelp.genesys.cloud
  2. FedRAMP compliancehelp.genesys.cloud
  3. Genesys Cloud Trust Center – Compliancegenesys.com
  4. AWS regions for Genesys Cloudhelp.genesys.cloud
  5. PCI DSS compliancehelp.genesys.cloud
  6. Secure flows overviewhelp.genesys.cloud
  7. Genesys deepens strategic collaboration with AWS (July 2026)genesys.com

Methods & templates

Security & compliance: the templates behind each stage

Every QVCCS engagement follows our seven-stage delivery lifecycle, each stage closed by a quality gate. For Security & compliance, the work concentrates in Discover, Define, Design, Prove, Transition and Run & evolve, and these are the techniques and standard templates we lean on there, each one traceable from requirement to design, build, test and support.

  1. 01DiscoverDiscovery sign-off
  2. 02DefineRequirements baseline
  3. 03DesignDesign authority review
  4. 04BuildBuild complete
  5. 05ProveGo / no-go readiness
  6. 06TransitionOperational acceptance
  7. 07Run & evolveService reviews
  • 1 · Discover

    Existing-org configuration audit

    Exports and reviews current roles, divisions, OAuth clients, recording and retention settings to find gaps before redesign.

  • 2 · Define

    Functional & Non-Functional Requirements Specification

    Captures each security, privacy, residency and retention obligation as a testable requirement traced through design to evidence.

  • 3 · Design

    Security and data-protection design

    Sets region, access model, secure flows, recording controls and integration credentials in the HLD and LLD for design authority.

  • 5 · Prove

    Negative and failure-path testing

    Proves personas cannot reach data outside their divisions and that sensitive values never appear in recordings, logs or exports.

  • 6 · Transition

    Operational handover pack

    Delivers as-built documentation, responsibility matrix and evidence so security and audit teams own an accurate picture.

  • 7 · Run & evolve

    Release impact assessments

    Reviews Genesys release notes against your controls so new features never quietly change your compliance position.

See the full QVCCS delivery method

How we deliver

Security & compliance: one accountable team, start to finish

  1. 01AssessReview your policies, obligations and control framework, and map them against Genesys Cloud platform assurances.
  2. 02DesignRegion, access, data protection, retention and integration security set out in signed-off high- and low-level designs.
  3. 03BuildCertified engineers configure roles, divisions, secure flows, retention and integration credentials exactly as designed.
  4. 04EvidencePersona-based access testing, data leakage checks and an organised evidence pack for auditors and assessors.
  5. 05GovernAccess reviews, change control and release impact assessment, with support aligned to your support model.

The specialists on this work, from our own bench

  • Enterprise Solution Architect
  • Solution Architect
  • Senior Business Consultant / Business Analyst
  • IT Systems, Telecoms & SIP Engineer
  • Systems Integration Tester
  • Senior Platform Practice Lead (Genesys Cloud CX)

Every engagement follows our seven-stage method, with design authority, engineering standards and four-eyes peer review behind it. How we deliver →

Questions

Security & compliance: common questions

Which compliance certifications does Genesys Cloud support?

Genesys lists PCI DSS, SOC 1 Type 2, SOC 2 Type 2, ISO 27001:2022, ISO 27017:2015, ISO 27018:2019, CSA CAIQ, C5, ISO 42001:2023 for AI and HIPAA support, with more on its Trust Center, such as SOC 3 and Cyber Essentials Plus. These are Genesys platform assurances. QVCCS helps you use them within your own control framework.

Does using Genesys Cloud make my contact centre compliant?

No platform can do that alone. Genesys secures and certifies the platform, while your organisation remains responsible for configuration, access, data handling, retention and processes. QVCCS designs and documents those client-side controls, and builds a responsibility matrix so it is clear who owns each requirement.

Is there a FedRAMP version of Genesys Cloud?

Yes. Genesys Cloud CX is FedRAMP authorised at the Class C (formerly Moderate) impact level, and Genesys supports FedRAMP only in the AWS US East 2 region. ISO 27001, 27017 and 27018 do not currently cover that region, and customers must follow Genesys's FedRAMP participant requirements, so we review which assurances, features and integrations apply before recommending it.

How should we design roles and divisions in Genesys Cloud?

Start from real job functions and organisational boundaries, not default templates. Divisions separate business units, brands or partners, while roles grant only the permissions each function needs. QVCCS models both with your teams, tests them with realistic personas and documents the result for ongoing access reviews.

Last reviewed

Talk to a specialist about this

We work by introduction. Clients, partners and people introduced to us can reach the right specialist for this topic directly.

Who to contact