Cloudry

Cloudry Trust Center

See how Cloudry verifies the systems it manages

Cloudry publishes the checks behind the applications and infrastructure we manage. This dashboard shows what we check, when it was last verified, and the result of each check.

A passing control means that specific check met its defined requirement.

Current verification

1 controls verified5 awaiting public evidence

0 controls currently need attention.

5 evidence stale.

Not yet verified means Cloudry does not currently have enough published information to verify the control. It does not mean the control failed.

Latest control evaluation: .

Monitoring since .

What this means for your business

Cloudry regularly checks the systems we manage for secure connections, data protection, backups, reliability, software changes, and known vulnerabilities. This page shows what we can currently verify and the checks behind those results.

If a check is not yet verified or is still being built, we show that too.
  • Transport
    What it checks

    Checks whether Cloudry-managed public services use HTTPS, have a valid TLS certificate, and tell browsers to keep using secure connections.

    Why it matters

    These protections help keep information private while it travels between a visitor and a managed service.

    Evidence stale
    1 control
    HTTPS, TLS validity, and HSTSSEC-TRANSPORT-001

    Evaluated

    Fresh until

  • Data protection
    What it checks

    Checks whether managed applications use encrypted connections when they send information to and from a database.

    Why it matters

    Encryption helps protect business and customer data while it moves between the application and database.

    Evidence stale
    1 control
    Database connection encryptionSEC-DATA-001

    Evaluated

    Fresh until

  • Monitoring
    What it checks

    Checks whether public services respond, background workers report a current heartbeat, and required monitoring and alerts can be verified.

    Why it matters

    These checks help Cloudry spot service interruptions, stalled background work, and missing operational coverage.

    Monitoring does not include virus or malware scanning.
    Evidence unavailable
    3 controls
    Monitoring-agent and alert coverageMON-COVERAGE-001
    Public endpoint healthMON-ENDPOINT-001
    Background worker heartbeatMON-WORKER-001

    Evaluated

    Fresh until

  • Backup and recovery
    What it checks

    Checks backup freshness, host backup coverage, and recent recovery testing.

    Why it matters

    Backups reduce risk only when they are recent, cover the right systems, and can be restored.

    Evidence unavailable
    3 controls
    Database backup freshnessBKP-FRESH-001
    State-bearing host backupsBKP-HOST-001
    Restore drill currencyBKP-RESTORE-001

    Evaluated

    Fresh until

  • Change management
    What it checks

    Checks whether managed infrastructure is represented in code, software contents can be traced, and vulnerability scans are current.

    Why it matters

    Traceable changes and current scans help Cloudry review releases and respond to known software risks.

    Vulnerability scanning checks for known software weaknesses. It is not the same as virus or malware scanning.
    Evidence unavailable
    2 controls
    Terraform representationIAC-TERRAFORM-001
    Image provenance and SBOM currencyIAC-SBOM-001

    Evaluated

    Fresh until

  • Vulnerability scanning
    What it checks

    Checks whether Cloudry has current Dependabot reconciliation and signed Trivy results for the exact deployed production source map.

    Why it matters

    Current scanning helps Cloudry detect known software vulnerabilities, notify the owner, track remediation, and verify fixes after deployment.

    A verified result means vulnerability monitoring and source-bound scanning are current. It does not mean no vulnerabilities exist, and it does not scan for malware, viruses, or uploaded files. Only reviewed, scan-verified remediations may appear in public incident history.
    Evidence unavailable
    1 control
    Vulnerability scan currencyIAC-VULN-001

    Evaluated

    Fresh until

90-day verification history

Only real verification history is shown. Cloudry does not invent results for periods before monitoring began.

Collecting history since .

Transport

Data protection

Monitoring

Backup & recovery

Change management

Vulnerability monitoring

  • Verified
  • Warning
  • Manual review
  • Failure
  • Evidence unavailable
  • Not applicable

Explore checks and verification

Search by business concern, check, or framework.

How statuses work
Evidence stale
A previous verification exists, but it is older than the allowed freshness window.
Evidence unavailable
Cloudry does not have enough current public information to verify the control.
In development
Automated verification for this control is being built.
Manual review
The control currently depends on a documented human review.
Needs attention
A current check did not meet its defined requirement. Expanded details show the published machine state.
Not applicable
The control does not apply to the current environment.
Not connected
The control exists, but Cloudry has not connected the information needed to verify it.
Planned
This control family is planned for a future release.
Verified
Current checks support the published result.

Cloudry does not treat missing verification as a passing result.

Security & Access9 controls

How Cloudry protects connections, credentials, administrative access, and exposure to managed systems.

Secure connections2 controls
HTTPS and TLS protectionSEC-TRANSPORT-001Evidence staleEvaluatedFresh until
What this checks

Checks that public Cloudry-managed services use HTTPS, have a valid security certificate, and tell browsers to keep using secure connections.

Why it matters

This helps protect information while it travels between your customers' browsers and the systems Cloudry manages.

Technical title HTTPS, TLS validity, and HSTS

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
Raw status
PASS
Planned controls1
Certificate expiration monitoringPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Access and identity4 controls
Planned controls4
Privileged-access protectionPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
MFA coveragePlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Administrative access reviewPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Service credential rotationPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Network protection3 controls
Planned controls3
Public exposure checksPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Trusted-source rulesPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Firewall policy checksPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Privacy & Data Handling11 controls

How customer information is encrypted, separated, accessed, and handled inside managed systems.

Encryption3 controls
Encrypted database connectionsSEC-DATA-001Evidence staleEvaluatedFresh until
What this checks

Checks that applications use encrypted connections when sending information to and from their managed databases.

Why it matters

Encryption helps protect business and customer data while it moves between the application and database.

Technical title Database connection encryption

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
Raw status
PASS
Planned controls2
Encryption at restPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Secrets protectionPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Customer separation4 controls
Planned controls4
Tenant resource assignmentPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Unique tenant credentialsPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Cross-tenant isolationPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Tenant-specific storage boundariesPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Data handling4 controls
Planned controls4
Retention controlsPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Sensitive-data handlingPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Subprocessor recordsPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Data-access loggingPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Reliability, Backups & Recovery7 controls

Whether managed systems are available, monitored, backed up, and recoverable when something goes wrong.

Service health3 controls
Public endpoints are healthyMON-ENDPOINT-001Evidence staleEvaluatedFresh until
What this checks

Checks that the public web addresses Cloudry monitors respond with the expected health result.

Why it matters

A failed health check can be an early sign that customers cannot reach an application or that part of it is not working.

Technical title Public endpoint health

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
Raw status
PASS
Background workers are reportingMON-WORKER-001Evidence staleEvaluatedFresh until
What this checks

Checks that background processes responsible for work outside the browser are still reporting a current heartbeat.

Why it matters

A website can appear available while important background work has stopped. This check helps expose that gap.

Technical title Background worker heartbeat

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
Raw status
PASS
Monitoring and alert coverageMON-COVERAGE-001Evidence unavailableEvaluatedFresh until
What this checks

Checks that required servers report to Cloudry's monitoring system and have the expected resource alerts configured.

Why it matters

Monitoring and alerts help Cloudry notice missing coverage or resource pressure before it becomes a larger service problem.

Technical title Monitoring-agent and alert coverage

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
—
Raw status
UNKNOWN
Database protection1 control
Database backups are currentBKP-FRESH-001Evidence staleEvaluatedFresh until
What this checks

Checks whether the latest protected database backup falls within Cloudry's defined backup window.

Why it matters

A recent backup can limit the amount of work that must be recreated after data loss.

Technical title Database backup freshness

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
Raw status
PASS
Infrastructure backups1 control
Stateful host backup coverageBKP-HOST-001Evidence unavailableEvaluatedFresh until
What this checks

Checks that required systems which store persistent information have automated backup coverage and a recent backup record.

Why it matters

Some important data lives outside a managed database. This check helps confirm those systems are included in the backup plan.

Technical title State-bearing host backups

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
—
Raw status
UNKNOWN
Recovery testing2 controls
Recovery testing is currentBKP-RESTORE-001VerifiedEvaluatedFresh until
What this checks

Checks that Cloudry has recently tested recovery of protected data and recorded a result that met the published requirement.

Why it matters

A backup only helps when it can be restored. Recovery tests show whether the restore process worked when tested.

Technical title Restore drill currency

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
—
Raw status
PASS
Planned controls1
Recovery canary validationPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Software Integrity & Vulnerability Management8 controls

How Cloudry checks deployed software for known vulnerabilities, traceable build information, and unexpected changes.

Vulnerability scanning3 controls
Vulnerability scans are currentIAC-VULN-001Evidence unavailableEvaluatedFresh until
What this checks

Checks that required vulnerability scans ran within policy and did not leave an unresolved result that blocks launch.

Why it matters

Current scans help identify known software risks that may need to be fixed before a release moves forward.

Technical title Vulnerability scan currency

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
—
Raw status
UNKNOWN
Planned controls2
Dependency scanningPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Container and image scanningPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Software provenance3 controls
Image provenance and SBOM are currentIAC-SBOM-001Evidence unavailableEvaluatedFresh until
What this checks

Checks that governed runtime images have a current record of where they came from and which software components they contain.

Why it matters

Knowing what is inside a deployed image helps Cloudry trace changes and determine whether a newly disclosed software issue may apply.

Technical title Image provenance and SBOM currency

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
—
Raw status
UNKNOWN
Planned controls2
Deployment-to-source mappingPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Artifact digest verificationPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Malware and file protection2 controls
Planned controls2
Malware scanningIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Uploaded-file scanningIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Scalability & Resource Health13 controls

Whether managed infrastructure has enough capacity to operate reliably and whether Cloudry can detect resource pressure before it becomes a larger problem.

Resource monitoring5 controls
Planned controls5
CPU monitoringIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Memory monitoringIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Storage capacityIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Database capacityIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Database connection thresholdsIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Scaling policy4 controls
Planned controls4
Infrastructure reproducibilityIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Resource-alert coverageIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Scaling policy coverageIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Capacity threshold coverageIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Performance testing4 controls
Planned controls4
Load-test currencyIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Tested throughputIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Response-time targetsIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Performance regression checksIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Auditability & Change Control11 controls

Whether important infrastructure and software changes can be traced, reviewed, and reconstructed later.

Infrastructure as code3 controls
Infrastructure is defined through codeIAC-TERRAFORM-001Evidence unavailableEvaluatedFresh until
What this checks

Checks that managed production infrastructure is represented in version-controlled Terraform configuration.

Why it matters

A recorded infrastructure definition makes changes easier to review and helps Cloudry rebuild managed resources consistently.

Technical title Terraform representation

Published evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Observed
—
Raw status
UNKNOWN
Planned controls2
Configuration driftPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Managed-resource reconciliationPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Change history4 controls
Planned controls4
Deployment historyPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Administrative changesPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Policy-version historyPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Change approval and review historyPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Evidence integrity4 controls
Planned controls4
Append-only evaluation historyPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Evidence hashingPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Signed evaluationsPlanned

This control family is planned for a future release.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—
Transparency receiptsIn development

Automated verification for this control is being built.

Evidence
—
Evaluation date
—
Framework mappings
—
Technical proof
—

Framework mappings

Framework mappings show how Cloudry controls relate to published criteria. They are not independent certifications.

NIST CSF 2.05 mapped criteria

Shows how published Cloudry controls relate to selected NIST Cybersecurity Framework 2.0 outcomes. This mapping is not certification and does not represent full framework coverage.

CriterionDescriptionMapped controls
GV.RR-02Roles, responsibilities, and authoritiesIAC-TERRAFORM-001
PR.DS-02Data in transit is protectedSEC-DATA-001, SEC-TRANSPORT-001
DE.CM-01Networks and services are monitoredMON-COVERAGE-001, MON-ENDPOINT-001, MON-WORKER-001
ID.RA-01Vulnerabilities are identifiedIAC-SBOM-001, IAC-VULN-001
RC.RP-03Recovery plans are verifiedBKP-FRESH-001, BKP-HOST-001, BKP-RESTORE-001
SOC 2 criteria mapping4 mapped criteria

Shows how published Cloudry controls relate to selected AICPA Trust Services Criteria. This mapping is not an attestation or a statement of SOC 2 compliance.

CriterionDescriptionMapped controls
CC6.1Logical access securitySEC-DATA-001, SEC-TRANSPORT-001
CC7.2System monitoringIAC-VULN-001, MON-COVERAGE-001, MON-ENDPOINT-001, MON-WORKER-001
CC8.1Change managementIAC-SBOM-001, IAC-TERRAFORM-001
A1.2Recovery and backupBKP-FRESH-001, BKP-HOST-001, BKP-RESTORE-001
HIPAA-related safeguards5 mapped criteria

Shows how selected published Cloudry controls relate to safeguards in the current HIPAA Security Rule. This mapping does not establish that Cloudry or a customer is HIPAA compliant, a covered entity or business associate, or operating under a business associate agreement.

CriterionDescriptionMapped controls
164.308(a)(1)(ii)(A)Risk analysisIAC-SBOM-001, IAC-VULN-001
164.308(a)(7)(ii)(A)Data backup planBKP-FRESH-001, BKP-HOST-001
164.308(a)(7)(ii)(B)Disaster recovery planBKP-RESTORE-001
164.308(a)(7)(ii)(D)Testing and revision proceduresBKP-RESTORE-001
164.312(e)(1)Transmission securitySEC-DATA-001, SEC-TRANSPORT-001
ISO/IEC 27001 mapping6 mapped criteria

Shows how selected published Cloudry controls relate to ISO/IEC 27001:2022 Annex A reference controls. This mapping is not certification, an ISMS conformity assessment, or a statement of full framework coverage.

CriterionDescriptionMapped controls
A.5.30ICT readiness for business continuityBKP-RESTORE-001
A.8.8Management of technical vulnerabilitiesIAC-SBOM-001, IAC-VULN-001
A.8.9Configuration managementIAC-TERRAFORM-001
A.8.13Information backupBKP-FRESH-001, BKP-HOST-001
A.8.16Monitoring activitiesMON-COVERAGE-001, MON-ENDPOINT-001, MON-WORKER-001
A.8.24Use of cryptographySEC-DATA-001, SEC-TRANSPORT-001

How Cloudry verifies checks

Cloudry publishes a result only after the check runs, the needed results are gathered, and the outcome is evaluated and recorded.

  1. Scope set

    Cloudry identifies the managed applications and infrastructure included in each check.

  2. Checks run

    Defined checks run against those managed systems.

  3. Results gathered

    Cloudry gathers only the information needed to evaluate each check.

  4. Evaluated

    Published rules compare the results with each check's defined requirement.

  5. Published

    Reviewed results are recorded, sanitized, and published here. Supporting evidence remains available in the technical details.

Public evidence is narrower than Cloudry's internal operational record.

Independent verification

Cloudry is building toward downloadable proofs and open verification tools so selected results can be validated independently of this dashboard.

In development
  • Downloadable proof bundles
  • Evidence digest verification
  • Open verification tool
  • Transparency receipts
  • Signed evaluations

Backups are evaluated separately from recovery. A backup existing does not prove that it can be restored successfully.

Backup capabilityEvidence unavailable
Published evidence unavailableBKP-PITR-001

No public evidence summary is available.

Evaluated —

Backup freshnessEvidence stale
Database backup freshnessBKP-FRESH-001

No public evidence summary is available.

Evaluated

Host coverageEvidence unavailable
State-bearing host backupsBKP-HOST-001

No public evidence summary is available.

Evaluated

Recovery testingVerified
Restore drill currencyBKP-RESTORE-001

No public evidence summary is available.

Evaluated

Ongoing vulnerability response

Cloudry regularly scans deployed software for newly disclosed vulnerabilities. When a known issue applies to our environment, we track the fix and verify the remediation with a later passing scan.

Current scan status
Evidence unavailable
Latest verified remediation

Ongoing vulnerability response

Verified vulnerability remediations

This history shows vulnerabilities identified through routine scanning and later confirmed as resolved by a passing follow-up scan.

These are proactive scan findings, not security incidents or evidence that a vulnerability was exploited.

4 vulnerabilities resolved

4 / 4 fixes verified by follow-up scan

  • 4 High resolved

24 vulnerabilities resolved

24 / 24 fixes verified by follow-up scan

  • 19 High resolved
  • 5 Medium resolved

21 vulnerabilities resolved

21 / 21 fixes verified by follow-up scan

  • 14 High resolved
  • 7 Medium resolved

102 vulnerabilities resolved

102 / 102 fixes verified by follow-up scan

  • 58 High resolved
  • 44 Medium resolved

Security incident history

Material security incidents appropriate for public disclosure are published here after review.

Active

No reviewed active security incidents

Resolved

No reviewed resolved security incidents

How Cloudry operates managed systems

The operating patterns behind Cloudry-managed systems.

  • Infrastructure as code

    Managed infrastructure is defined and reproduced through Terraform and automated configuration.

  • Recorded operations

    Important infrastructure and deployment changes are retained in operational history.

  • Customer separation

    Managed environments use scoped resources and credentials appropriate to each organization.

  • Customer-specific controls

    Additional controls can be implemented and documented when a customer has specific security, privacy, or regulatory requirements.

What this dashboard does—and does not—prove

Read the evidence as a bounded operational record, not a blanket assurance.

This dashboard does

  • Publish defined operational controls
  • Show current evidence status
  • Preserve evaluation history
  • Expose gaps instead of hiding them
  • Map selected controls to relevant frameworks
  • Distinguish evidence from certification

This dashboard does not

  • Claim that vulnerabilities cannot exist
  • Replace an independent audit
  • Automatically establish legal compliance
  • Expose sensitive infrastructure details publicly
  • Treat missing evidence as proof

Questions about security or a Cloudry control?

Report a security concern, ask how a control applies to your project, or request security documentation.

Contact security

Eleven public checks

What Cloudry checks

These eleven checks show what Cloudry can currently verify. Open a check to see what it covers, why it matters to your business, and the published result.

HTTPS and TLS protectionTransportEvidence stale
What this checks

Checks that public Cloudry-managed services use HTTPS, have a valid security certificate, and tell browsers to keep using secure connections.

Why it matters

This helps protect information while it travels between your customers' browsers and the systems Cloudry manages.

Published result
Evidence stale
Evaluated
Fresh until
Technical title
HTTPS, TLS validity, and HSTS
Control code
SEC-TRANSPORT-001
Raw status
PASS
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Encrypted database connectionsData protectionEvidence stale
What this checks

Checks that applications use encrypted connections when sending information to and from their managed databases.

Why it matters

Encryption helps protect business and customer data while it moves between the application and database.

Published result
Evidence stale
Evaluated
Fresh until
Technical title
Database connection encryption
Control code
SEC-DATA-001
Raw status
PASS
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Monitoring and alert coverageMonitoringEvidence unavailable
What this checks

Checks that required servers report to Cloudry's monitoring system and have the expected resource alerts configured.

Why it matters

Monitoring and alerts help Cloudry notice missing coverage or resource pressure before it becomes a larger service problem.

Published result
Evidence unavailable
Evaluated
Fresh until
Technical title
Monitoring-agent and alert coverage
Control code
MON-COVERAGE-001
Raw status
UNKNOWN
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Public endpoints are healthyMonitoringEvidence stale
What this checks

Checks that the public web addresses Cloudry monitors respond with the expected health result.

Why it matters

A failed health check can be an early sign that customers cannot reach an application or that part of it is not working.

Published result
Evidence stale
Evaluated
Fresh until
Technical title
Public endpoint health
Control code
MON-ENDPOINT-001
Raw status
PASS
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Background workers are reportingMonitoringEvidence stale
What this checks

Checks that background processes responsible for work outside the browser are still reporting a current heartbeat.

Why it matters

A website can appear available while important background work has stopped. This check helps expose that gap.

Published result
Evidence stale
Evaluated
Fresh until
Technical title
Background worker heartbeat
Control code
MON-WORKER-001
Raw status
PASS
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Database backups are currentBackup and recoveryEvidence stale
What this checks

Checks whether the latest protected database backup falls within Cloudry's defined backup window.

Why it matters

A recent backup can limit the amount of work that must be recreated after data loss.

Published result
Evidence stale
Evaluated
Fresh until
Technical title
Database backup freshness
Control code
BKP-FRESH-001
Raw status
PASS
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Stateful host backup coverageBackup and recoveryEvidence unavailable
What this checks

Checks that required systems which store persistent information have automated backup coverage and a recent backup record.

Why it matters

Some important data lives outside a managed database. This check helps confirm those systems are included in the backup plan.

Published result
Evidence unavailable
Evaluated
Fresh until
Technical title
State-bearing host backups
Control code
BKP-HOST-001
Raw status
UNKNOWN
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Recovery testing is currentBackup and recoveryVerified
What this checks

Checks that Cloudry has recently tested recovery of protected data and recorded a result that met the published requirement.

Why it matters

A backup only helps when it can be restored. Recovery tests show whether the restore process worked when tested.

Published result
Verified
Evaluated
Fresh until
Technical title
Restore drill currency
Control code
BKP-RESTORE-001
Raw status
PASS
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Infrastructure is defined through codeChange managementEvidence unavailable
What this checks

Checks that managed production infrastructure is represented in version-controlled Terraform configuration.

Why it matters

A recorded infrastructure definition makes changes easier to review and helps Cloudry rebuild managed resources consistently.

Published result
Evidence unavailable
Evaluated
Fresh until
Technical title
Terraform representation
Control code
IAC-TERRAFORM-001
Raw status
UNKNOWN
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Image provenance and SBOM are currentChange managementEvidence unavailable
What this checks

Checks that governed runtime images have a current record of where they came from and which software components they contain.

Why it matters

Knowing what is inside a deployed image helps Cloudry trace changes and determine whether a newly disclosed software issue may apply.

Published result
Evidence unavailable
Evaluated
Fresh until
Technical title
Image provenance and SBOM currency
Control code
IAC-SBOM-001
Raw status
UNKNOWN
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.
Vulnerability scans are currentChange managementEvidence unavailable
What this checks

Checks that required vulnerability scans ran within policy and did not leave an unresolved result that blocks launch.

Why it matters

Current scans help identify known software risks that may need to be fixed before a release moves forward.

Published result
Evidence unavailable
Evaluated
Fresh until
Technical title
Vulnerability scan currency
Control code
IAC-VULN-001
Raw status
UNKNOWN
Supporting evidence
Evidence unavailable.
Evidence source
Sanitized public evidence from the Trust controls API.