ClairvoyantIntelligence, Inc.

At Clairvoyant, our security practices are regularly reviewed by independent auditors, who evaluate our controls across key areas such as data protection, availability, confidentiality, and privacy. This rigorous process demonstrates our dedication to safeguarding customer information and maintaining transparency–so you can trust Clairvoyant to keep your software supply chain secure.

Customers and external users may use [email protected] to report any actual or suspected security, confidentiality, data integrity, or service availability issue related to Clairvoyant services. Reports sent to this address are monitored by Clairvoyant’s security and incident response personnel.

[email protected]

An illustrative product view: expected versus detected behaviors for a sample application, grouped into four categories with findings per category.

Risk ContextATT&CK

Expected vs detected – TaxDoc 1.0.0.30000

4Categories exceeded
0Within expectations
14Total findings
Data Access

Derived from application category and vendor profile.

Network Communication

Derived from application category and vendor profile.

System Interaction

Standard for a document application. Privilege escalation and event log access are not expected.

User Interface

Derived from application category and vendor profile.

Expected behaviours derived from application category and vendor profile analysis

Attestations

Audited against the SOC 2 trust services criteria.

Attestation

SOC 2 Type I

Design of controls, assessed at a point in time by an independent auditor.

Attestation

SOC 2 Type II

Operating effectiveness of controls, observed over a period by an independent auditor.

Clairvoyant Intelligence is the Enterprise Software Control Plane for your software perimeter. It provides independent, pre‑approval insight into software wherever it originates or runs—across vendors, pipelines, and internal AI‑driven development—so enterprises can reduce reliance on attestations and ensure only trusted software runs in their environment.

Compliance

SOC 2 Type I
SOC 2 Type II

Controls

Updated recently

Infrastructure security

  • Unique production database authentication enforced
  • Encryption key access restricted
  • Unique account authentication enforced

Organizational security

  • Production inventory maintained
  • Portable media encrypted
  • Anti-malware technology utilized

Product security

  • Data encryption utilized
  • Control self-assessments conducted
  • Penetration testing performed

Internal security procedures

  • Continuity and Disaster Recovery plans established
  • Continuity and Disaster Recovery plans tested
  • Cybersecurity insurance maintained

Data and privacy

  • Data retention procedures established
  • Customer data deleted upon leaving
  • Data classification policy established

Controls

Updated recently

Infrastructure security

  • Unique production database authentication enforced

    The company requires authentication to production datastores to use authorized secure authentication mechanisms, such as unique SSH key.

  • Encryption key access restricted

    The company restricts privileged access to encryption keys to authorized users with a business need.

  • Unique account authentication enforced

    The company requires authentication to systems and applications to use unique username and password or authorized Secure Socket Shell (SSH) keys.

  • Production application access restricted

    System access restricted to authorized access only

  • Access control procedures established
  • Production database access restricted

    The company restricts privileged access to databases to authorized users with a business need.

  • Firewall access restricted

    The company restricts privileged access to the firewall to authorized users with a business need.

  • Production OS access restricted

    The company restricts privileged access to the operating system to authorized users with a business need.

  • Production network access restricted

    The company restricts privileged access to the production network to authorized users with a business need.

  • Access revoked upon termination

    The company completes termination checklists to ensure that access is revoked for terminated employees within SLAs.

  • Unique network system authentication enforced

    The company requires authentication to the production network to use unique usernames and passwords or authorized Secure Socket Shell (SSH) keys.

  • Remote access MFA enforced
  • Remote access encrypted enforced
  • Intrusion detection system utilized
  • Log management utilized
  • Infrastructure performance monitored

    An infrastructure monitoring tool is utilized to monitor systems, infrastructure, and performance and generates alerts when specific predefined thresholds are met.

  • Network segmentation implemented
  • Network firewalls reviewed

    The company reviews its firewall rulesets at least annually. Required changes are tracked to completion.

  • Network firewalls utilized

    The company uses firewalls and configures them to prevent unauthorized access.

  • Network and system hardening standards maintained
  • Service infrastructure maintained

    The company has infrastructure supporting the service patched as a part of routine maintenance and as a result of identified vulnerabilities to help ensure that servers supporting the service are hardened against security threats.

Organizational security

  • Production inventory maintained

    The company maintains a formal inventory of production system assets.

  • Portable media encrypted

    The company encrypts portable and removable media devices when used.

  • Anti-malware technology utilized

    The company deploys anti-malware technology to environments commonly susceptible to malicious attacks and configures this to be updated routinely, logged, and installed on all relevant systems.

  • Employee background checks performed

    The company performs background checks on new employees.

  • Code of Conduct acknowledged by contractors

    The company requires contractor agreements to include a code of conduct or reference to the company code of conduct.

  • Code of Conduct acknowledged by employees and enforced

    The company requires employees to acknowledge a code of conduct at the time of hire. Employees who violate the code of conduct are subject to disciplinary actions in accordance with a disciplinary policy.

  • Confidentiality Agreement acknowledged by contractors

    The company requires contractors to sign a confidentiality agreement at the time of engagement.

  • Confidentiality Agreement acknowledged by employees

    The company requires employees to sign a confidentiality agreement during onboarding.

  • Performance evaluations conducted

    The company managers are required to complete performance evaluations for direct reports at least annually.

  • Password policy enforced
  • MDM system utilized

    The company has a mobile device management (MDM) system in place to centrally manage mobile devices supporting the service.

  • Visitor procedures enforced

    The company requires visitors to sign-in, wear a visitor badge, and be escorted by an authorized employee when accessing the data center or secure areas.

  • Security awareness training implemented

    The company requires employees to complete security awareness training within thirty days of hire and at least annually thereafter.

Product security

  • Data encryption utilized
  • Control self-assessments conducted

    The company performs control self-assessments at least annually to gain assurance that controls are in place and operating effectively. Corrective actions are taken based on relevant findings. If the company has committed to an SLA for a finding, the corrective action is completed within that SLA.

  • Penetration testing performed
  • Data transmission encrypted

    The company uses secure data transmission protocols to encrypt confidential and sensitive data when transmitted over public networks.

  • Vulnerability and system monitoring procedures established

Internal security procedures

  • Continuity and Disaster Recovery plans established

    The company has Business Continuity and Disaster Recovery Plans in place that outline communication plans in order to maintain information security continuity in the event of the unavailability of key personnel.

  • Continuity and Disaster Recovery plans tested

    The company has a documented Business Continuity/Disaster Recovery (BC/DR) plan and tests it at least annually.

  • Cybersecurity insurance maintained

    The company maintains cybersecurity insurance to mitigate the financial impact of business disruptions.

  • Configuration management system established

    The company has a configuration management procedure in place to ensure that system configurations are deployed consistently throughout the environment.

  • Change management procedures enforced

    The company requires changes to software and infrastructure components of the service to be authorized, formally documented, tested, reviewed, and approved prior to being implemented in the production environment.

  • Production deployment access restricted

    The company restricts access to migrate changes to production to authorized personnel.

  • Development lifecycle established

    The company has a formal systems development life cycle (SDLC) methodology in place that governs the development, acquisition, implementation, changes (including emergency changes), and maintenance of information systems and related technology requirements.

  • SOC 2 - System Description
  • Whistleblower policy established

    The company has established a formalized whistleblower policy, and an anonymous communication channel is in place for users to report potential issues or fraud concerns.

  • Board oversight briefings conducted
  • Board charter documented
  • Board expertise developed
  • Board meetings conducted
  • Backup processes established
  • System changes externally communicated

    The company notifies customers of critical system changes that may affect their processing.

  • Management roles and responsibilities defined

    The company management has established defined roles and responsibilities to oversee the design and implementation of information security controls.

  • Organization structure documented

    The company maintains an organizational chart that describes the organizational structure and reporting lines.

  • Roles and responsibilities specified

    Roles and responsibilities for the design, development, implementation, operation, maintenance, and monitoring of information security controls are formally assigned in job descriptions and/or the Roles and Responsibilities policy.

  • Security policies established and reviewed
  • Support system available

    The company has an external-facing support system in place that allows users to report system information on failures, incidents, concerns, and other complaints to appropriate personnel.

  • System changes communicated

    The company communicates system changes to authorized internal users.

  • Access reviews conducted

    The company conducts access reviews at least quarterly for the in-scope system components to help ensure that access is restricted appropriately. Required changes are tracked to completion.

  • Access requests required

    The company ensures that user access to in-scope system components is based on job role and function or requires a documented access request form and manager approval prior to access being provisioned.

  • Incident response plan tested

    The company tests their incident response plan at least annually.

  • Incident response policies established

    The company has security and privacy incident response policies and procedures that are documented and communicated to authorized users.

  • Incident management procedures followed
  • Physical access processes established

    The company has processes in place for granting, changing, and terminating physical access to company data centers based on an authorization from control owners.

  • Data center access reviewed

    The company reviews access to the data centers at least annually.

  • Company commitments externally communicated
  • External support resources available

    The company provides guidelines and technical support resources relating to system operations to customers.

  • Service description communicated

    The company provides a description of its products and services to internal and external users.

  • Risk assessment objectives specified

    The company specifies its objectives to enable the identification and assessment of risk related to the objectives.

  • Risks assessments performed
  • Risk management program established

    The company has a documented risk management program in place that includes guidance on the identification of potential threats, rating the significance of the risks associated with the identified threats, and mitigation strategies for those risks.

  • Third-party agreements established

    The company has written agreements in place with vendors and related third-parties. These agreements include confidentiality and privacy commitments applicable to that entity.

  • Vendor management program established
  • Vulnerabilities scanned and remediated

    Host-based vulnerability scans are performed at least quarterly on all external-facing systems. Critical and high vulnerabilities are tracked to remediation.

Data and privacy

  • Data retention procedures established

    The company has formal retention and disposal procedures in place to guide the secure retention and disposal of company and customer data.

  • Customer data deleted upon leaving

    The company purges or removes customer data containing confidential information from the application environment, in accordance with best practices, when customers leave the service.

  • Data classification policy established

    The company has a data classification policy in place to help ensure that confidential data is properly secured and restricted to authorized personnel.

Subprocessors

  • Amazon Web ServicesCloud providerUnited States

Data and disclosure

What the platform holds, who processes it, and how to reach us.

Service

Clairvoyant Intelligence is the Enterprise Software Control Plane for your software perimeter. It provides independent, pre‑approval insight into software wherever it originates or runs — across vendors, pipelines, and internal AI‑driven development.

Data collected

Customer personally identifiable information · employee personally identifiable information · credit card information · personal health information

Subprocessors

Amazon Web Services — cloud provider, United States

Security reporting

Customers and external users may report any actual or suspected security, confidentiality, data integrity, or service availability issue related to Clairvoyant services. [email protected]