CERYNZA TRUST CENTER

Security claims should come with a verification path.

Use this Trust Center to understand the control areas CERYNZA documents during architecture review, technical validation, deployment, and ongoing operations.

Trust through precise disclosure. This page does not imply a certification or feature that has not been independently verified. Request the evidence relevant to your deployment and procurement process.

ASSURANCE AREAS

What enterprise reviewers need to examine.

Each area should map to current documentation, responsible owners, review dates, and deployment-specific evidence.

Security architecture

  • Secure development and release process
  • Vulnerability and dependency management
  • Environment separation
  • Security validation and remediation

Data security

  • Encryption in transit and at rest
  • Tenant and access boundaries
  • Retention and deletion controls
  • Backup and recovery

Identity and access

  • Role-based access control
  • MFA and SSO requirements
  • Session and privileged access
  • Administrative audit evidence

AI data handling

  • Model and inference location
  • Customer data ownership
  • Training and retention policy
  • Human review and guardrails

Deployment assurance

  • On-premises and private cloud
  • Hybrid and data residency
  • Availability and disaster recovery
  • Air-gap requirements where supported

Policy and disclosure

  • Privacy and data handling
  • Responsible disclosure
  • Legal and service documents
  • Security contact and response process
RESPONSIBLE DISCLOSURE

Report a potential security issue directly.

Send enough detail to reproduce and assess the issue. Do not access, alter, or retain data that does not belong to you, and avoid actions that degrade service.

Email security@cerynza.com
Machine-readable contact/.well-known/security.txt
Preferred languages
English, Thai
Policy
Coordinated disclosure
Scope
CERYNZA public services and approved products
PROCUREMENT EVIDENCE

Ask for evidence that matches your risk.

Security questionnaires are a starting point. Architecture, test results, operational procedures, and responsibility boundaries make the answer useful.

Architecture and data-flow documentation
Secure development and release evidence
Vulnerability management process
Access-control and audit design
AI data handling and model boundary
Backup, recovery, and resilience plan
Penetration and security test scope
Deployment responsibility matrix
TECHNICAL VALIDATION

Bring your security questionnaire—and your architecture.

Review the controls, evidence, responsibilities, and deployment boundaries relevant to your organization.