Globeholder AI

Globeholder AI

Trust Center

Scientific AI agents that investigate, reason and deliver auditable, decision-grade intelligence for critical planetary decisions.

Controls

Comprehensive overview of the security control frameworks we run — grouped by category so you can jump straight to the domain you care about.

Control Environment

  • Code of Conduct acknowledged by employees and enforced

    Employees are required to acknowledge the code of conduct upon hiring. Any violations may result in disciplinary action as outlined in the company’s disciplinary policy.

  • Board oversight briefings conducted (SOC 2)

    Senior management briefs the board of directors, or an appropriate subcommittee, at least once a year on the company’s cybersecurity and privacy risk posture. The board offers guidance and feedback to management as necessary.

  • Audit controls implemented

    The company has implemented hardware, software, and procedural mechanisms to log and review activity within information systems that store or process electronic Protected Health Information (ePHI).

  • Security awareness training implemented

    Employees are required to complete security awareness training within 30 days of being hired and at least once a year thereafter.

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Employee background checks performed

    The company conducts background screenings for all new hires.

  • Board meetings conducted

    The board of directors meets at least once a year and keeps formal minutes of its meetings. It includes members who are independent of the company.

  • Board charter documented

    The board of directors has a formal charter that defines its oversight responsibilities related to internal controls.

  • Compliance with policies, rules and standards for information security

    The organization conducts regular reviews to ensure compliance with its information security policy, topic-specific policies, rules, and standards.

  • Board expertise developed

    The board possesses the necessary expertise to oversee management’s design, implementation, and operation of information security controls, and consults external security experts when needed.

  • Code of Conduct acknowledged by contractors

    The company mandates that contractor agreements either include a code of conduct or refer to the company’s own code of conduct.

  • Performance evaluations conducted

    Managers are required to conduct performance evaluations for their direct reports at least once a year.

Communication and Information

  • Code of Conduct acknowledged by employees and enforced

    Employees are required to acknowledge the code of conduct upon hiring. Any violations may result in disciplinary action as outlined in the company’s disciplinary policy.

  • Data integrity maintained

    The company has implemented policies and procedures to safeguard electronic Protected Health Information (ePHI) against unauthorized alteration or destruction.

  • Third-party agreements established

    The company maintains written agreements with vendors and third parties, which include applicable confidentiality and privacy commitments.

  • System changes communicated

    The company notifies authorized internal users of system changes.

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • System changes externally communicated

    The company informs customers of critical system changes that could impact their processing.

Risk Assessment

  • Risk assessment objectives specified

    The company defines its objectives to support the identification and assessment of risks associated with achieving them.

  • Risks assessments performed

    The company performs risk assessments at least annually. This process includes identifying threats and changes (environmental, regulatory, and technological) that may affect service commitments, formally assessing the related risks, and considering how potential fraud could impact the achievement of objectives.

  • Annual risk assessment performed annually

    The company performs the risk assessment process at least annually and whenever significant changes occur in the environment, such as acquisitions, mergers, or relocations.

  • Infrastructure performance monitored

    The company uses an infrastructure monitoring tool to track systems, infrastructure, and performance, generating alerts when predefined thresholds are reached.

  • Audit controls implemented

    The company has implemented hardware, software, and procedural mechanisms to log and review activity within information systems that store or process electronic Protected Health Information (ePHI).

  • Change management procedures enforced

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

  • Risk management program established

    The company maintains a documented risk management program that provides guidance on identifying potential threats, assessing the significance of associated risks, and implementing mitigation strategies.

  • Compliance with policies, rules and standards for information security

    The organization conducts regular reviews to ensure compliance with its information security policy, topic-specific policies, rules, and standards.

Monitoring Activities

  • Board oversight briefings conducted (SOC 2)

    Senior management briefs the board of directors, or an appropriate subcommittee, at least once a year on the company’s cybersecurity and privacy risk posture. The board offers guidance and feedback to management as necessary.

  • Audit controls implemented

    The company has implemented hardware, software, and procedural mechanisms to log and review activity within information systems that store or process electronic Protected Health Information (ePHI).

  • Security controls evaluated

    The company conducts periodic technical and nontechnical evaluations, initially based on the HIPAA Security Rule, and subsequently in response to environmental or operational changes affecting the security of electronic Protected Health Information (ePHI), to determine whether its security policies and procedures continue to meet the requirements of the HIPAA Security Rule (Subpart C).

  • Nonconformity and corrective action

    When a nonconformity is identified, the organization: 1. Responds to the issue by: a) Taking action to control and correct it b) Addressing any resulting consequences 2. Assesses the need for action to prevent recurrence or occurrence elsewhere by: a) Reviewing the nonconformity b) Identifying its root causes c) Determining whether similar issues exist or could potentially arise 3. Implements necessary corrective actions 4. Evaluates the effectiveness of those actions 5. Updates the information security management system as needed Corrective actions are proportionate to the impact of the nonconformities. Documented information is retained to demonstrate: 1. The nature of the nonconformities and the actions taken 2. The results of any corrective actions

  • Critical system review performed quarterly (SOC 2)

    For service providers, the company performs reviews at least quarterly to confirm personnel comply with security policies and operational procedures.

Control Activities

  • Audit controls implemented

    The company has implemented hardware, software, and procedural mechanisms to log and review activity within information systems that store or process electronic Protected Health Information (ePHI).

  • Development lifecycle established

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

  • Security controls evaluated

    The company conducts periodic technical and nontechnical evaluations, initially based on the HIPAA Security Rule, and subsequently in response to environmental or operational changes affecting the security of electronic Protected Health Information (ePHI), to determine whether its security policies and procedures continue to meet the requirements of the HIPAA Security Rule (Subpart C).

  • Documentation change control

    System documentation shall be subject to revision and change control procedures that maintain an audit trail documenting time-sequenced development and modifications.

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Risk management program established

    The company maintains a documented risk management program that provides guidance on identifying potential threats, assessing the significance of associated risks, and implementing mitigation strategies.

  • Compliance with policies, rules and standards for information security

    The organization conducts regular reviews to ensure compliance with its information security policy, topic-specific policies, rules, and standards.

  • Operational system checks

    Operational system checks shall be used, as appropriate, to enforce permitted sequencing of steps and events.

Logical and Physical Access Controls

  • Network firewalls utilized

    The company uses firewalls configured to block unauthorized access.

  • Asset disposal procedures utilized

    The company ensures electronic media containing confidential information is purged or destroyed following best practices, with certificates of destruction issued for each device.

  • Securely dispose of data (SOC 2)

    The organization securely disposes of data in accordance with the documented data management process, ensuring that disposal methods are appropriate for the sensitivity of the data.

  • Data center access reviewed

    The company reviews data center access at least once a year.

  • Network segmentation implemented

    The company’s network is segmented to block unauthorized access to customer data.

  • Data encryption utilized

    The company encrypts datastores containing sensitive customer data at rest.

  • Malicious software protection implemented

    The company has implemented procedures to guard against, detect, and report malicious software.

  • Password policy enforced

    The company requires passwords for in-scope system components to be configured in accordance with its policy.

  • Remote access encrypted enforced

    The company restricts remote access to production systems to authorized employees using an approved encrypted connection.

  • Security patches installed within one month

    The company installs critical security patches within one month of their release, as determined by the risk ranking process defined in VPM-4.

  • Intrusion detection system utilized

    The company uses an intrusion detection system to continuously monitor its network and detect potential security breaches early.

  • Access control procedures established

    The company’s access control policy outlines requirements for the following access control functions: 1. Adding new users 2. Modifying users 3. Removing user access

  • Production data segmented

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

  • System access limitation

    System access shall be restricted to authorized individuals.

  • Data transmission encrypted

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

  • Authority checks

    Authority checks shall restrict system use, electronic signing, access to operations or system input/output devices, record alteration, and performance of the operation at hand to authorized individuals.

  • Firewall access restricted

    The company limits privileged access to the firewall to authorized users who have a valid business need.

  • Data deletion requests handled

    The company validates deletion requests, and once confirmed, flags and deletes the requested information in accordance with applicable laws and regulations.

System Operations

  • Continuity and disaster recovery plans tested

    The company has a documented Business Continuity and Disaster Recovery (BC/DR) plan, which is tested at least once a year.

  • Contingency plan established

    The company has established and implements, as needed, policies and procedures for responding to emergencies or other events (such as fire, vandalism, system failure, or natural disaster) that may damage systems containing electronic Protected Health Information (ePHI).

  • Incident management procedures followed

    The company’s security and privacy incidents are logged, tracked, resolved, and communicated to affected or relevant parties by management in accordance with its security incident response policy and procedures.

  • Log management utilized

    The company uses a log management tool to detect events that could potentially affect its ability to meet security objectives.

  • Infrastructure performance monitored

    The company uses an infrastructure monitoring tool to track systems, infrastructure, and performance, generating alerts when predefined thresholds are reached.

  • Audit controls implemented

    The company has implemented hardware, software, and procedural mechanisms to log and review activity within information systems that store or process electronic Protected Health Information (ePHI).

  • Vulnerability and system monitoring procedures established

    The company’s formal policies define requirements for the following IT and engineering functions: 1. Vulnerability management 2. System monitoring

  • Intrusion detection system utilized

    The company uses an intrusion detection system to continuously monitor its network and detect potential security breaches early.

  • Incident response plan tested

    The company tests its incident response plan at least once a year.

  • Security vulnerabilities identification process exists

    The company maintains a process for identifying security vulnerabilities that includes: 1. Using reputable external sources to obtain current vulnerability information 2. Assigning risk rankings to identified vulnerabilities, clearly highlighting all high-risk and critical issues Risk rankings follow industry best practices and consider factors such as CVSS base scores, vendor classifications, and the affected system types. The risk assessment strategy ensures that all high-risk vulnerabilities are identified and that critical vulnerabilities, including those impacting public-facing systems, security infrastructure, or systems processing cardholder data, are addressed promptly.

  • Incident response policies established

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

Change Management

  • Change management procedures enforced

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

  • Development lifecycle established

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

  • Documentation change control

    System documentation shall be subject to revision and change control procedures that maintain an audit trail documenting time-sequenced development and modifications.

  • Production deployment access restricted

    The company restricts production change migrations to authorized personnel only.

Risk Mitigation

  • Continuity and disaster recovery plans tested

    The company has a documented Business Continuity and Disaster Recovery (BC/DR) plan, which is tested at least once a year.

  • Third-party agreements established

    The company maintains written agreements with vendors and third parties, which include applicable confidentiality and privacy commitments.

  • Contingency plan established

    The company has established and implements, as needed, policies and procedures for responding to emergencies or other events (such as fire, vandalism, system failure, or natural disaster) that may damage systems containing electronic Protected Health Information (ePHI).

  • Risks assessments performed

    The company performs risk assessments at least annually. This process includes identifying threats and changes (environmental, regulatory, and technological) that may affect service commitments, formally assessing the related risks, and considering how potential fraud could impact the achievement of objectives.

  • Vendor management program established

    The company has a vendor management program in place that includes: 1. Critical third-party vendor inventory 2. Vendor security and privacy requirements 3. Review of critical third-party vendors at least annually

  • Risk management program established

    The company maintains a documented risk management program that provides guidance on identifying potential threats, assessing the significance of associated risks, and implementing mitigation strategies.

Additional Criteria for Availability

  • Continuity and disaster recovery plans tested

    The company has a documented Business Continuity and Disaster Recovery (BC/DR) plan, which is tested at least once a year.

  • Contingency plan established

    The company has established and implements, as needed, policies and procedures for responding to emergencies or other events (such as fire, vandalism, system failure, or natural disaster) that may damage systems containing electronic Protected Health Information (ePHI).

  • Infrastructure performance monitored

    The company uses an infrastructure monitoring tool to track systems, infrastructure, and performance, generating alerts when predefined thresholds are reached.

  • Environmental monitoring devices implemented

    The company uses environmental monitoring devices configured to automatically alert management in the event of environmental incidents.

  • Database replication utilized

    The company’s databases are replicated in real time to a secondary data center, with alerts set up to notify administrators of any replication failures.

  • Incident response plan tested

    The company tests its incident response plan at least once a year.

  • Production data backups conducted

    The company performs periodic backups of production data, storing the backups in a separate location from the production environment.

  • Production multi-availability zones established

    The company employs a multi-location strategy for production environments to enable operations to resume at alternate data centers if a facility becomes unavailable.

  • Critical system review performed quarterly (SOC 2)

    For service providers, the company performs reviews at least quarterly to confirm personnel comply with security policies and operational procedures.

Additional Criteria for Confidentiality

  • Asset disposal procedures utilized

    The company ensures electronic media containing confidential information is purged or destroyed following best practices, with certificates of destruction issued for each device.

  • Securely dispose of data (SOC 2)

    The organization securely disposes of data in accordance with the documented data management process, ensuring that disposal methods are appropriate for the sensitivity of the data.

  • Data classification policy established

    The company has a data classification policy to ensure confidential data is properly secured and accessible only to authorized personnel.

  • Data encryption utilized

    The company encrypts datastores containing sensitive customer data at rest.

  • Production data segmented

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

  • Data deletion requests handled

    The company validates deletion requests, and once confirmed, flags and deletes the requested information in accordance with applicable laws and regulations.

Additional Criteria for Processing integrity

  • Data integrity maintained

    The company has implemented policies and procedures to safeguard electronic Protected Health Information (ePHI) against unauthorized alteration or destruction.

  • Establish and maintain a data management process (SOC 2)

    The organization establishes and maintains a documented data management process that addresses, at a minimum: 1. Data sensitivity 2. Data owner 3. Data handling 4. Data retention limits 5. Data disposal requirements The organization aligns these elements with enterprise sensitivity and retention standards and reviews and updates the documentation annually or upon significant changes that could impact this control.

  • System validation

    Persons who use closed systems to create, modify, maintain, or transmit electronic records shall validate those systems for accuracy, reliability, consistent intended performance, and the ability to detect invalid or altered records.

  • Customer data retained

    The company retains customer transaction data for the duration of the customer account. Historical transaction data is not purged until the account is deleted.

  • Production data backups conducted

    The company performs periodic backups of production data, storing the backups in a separate location from the production environment.

  • Compliance with policies, rules and standards for information security

    The organization conducts regular reviews to ensure compliance with its information security policy, topic-specific policies, rules, and standards.

  • Processing data inputs validated

    The company’s system evaluates data inputs for compliance with input requirements and generates on-screen alerts when issues with transaction inputs or processing are detected.

  • Operational system checks

    Operational system checks shall be used, as appropriate, to enforce permitted sequencing of steps and events.

Context of the organization

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Risk management program established

    The company maintains a documented risk management program that provides guidance on identifying potential threats, assessing the significance of associated risks, and implementing mitigation strategies.

  • Risks assessments performed

    The company performs risk assessments at least annually. This process includes identifying threats and changes (environmental, regulatory, and technological) that may affect service commitments, formally assessing the related risks, and considering how potential fraud could impact the achievement of objectives.

  • Understanding the needs and expectations of interested parties

    Because of their effect or potential effect on the organization’s ability to consistently deliver products and services that meet customer and applicable statutory and regulatory requirements, the organization shall determine: 1. The interested parties relevant to the quality management system 2. The requirements of these interested parties relevant to the quality management system The organization shall monitor and review information about these interested parties and their requirements.

  • Determining the scope of the quality management system

    The organization shall define the boundaries and applicability of the quality management system to establish its scope. In doing so, it shall consider: 1. External and internal issues identified in CPL-77 2. Requirements of relevant interested parties identified in AST-109 3. The organization’s products and services All applicable requirements of this International Standard shall be included within the defined scope. The scope shall be documented, maintained, and available. It shall state the products and services covered and justify any requirements deemed not applicable. Conformity may only be claimed if exclusions do not affect the organization’s ability or responsibility to ensure product and service conformity or to enhance customer satisfaction.

Leadership

  • Board oversight briefings conducted (SOC 2)

    Senior management briefs the board of directors, or an appropriate subcommittee, at least once a year on the company’s cybersecurity and privacy risk posture. The board offers guidance and feedback to management as necessary.

  • Roles and responsibilities specified

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

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Information security policy reviewed annually

    The company reviews the security policy at least annually and updates it whenever there are changes to the environment.

Planning

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Risk management program established

    The company maintains a documented risk management program that provides guidance on identifying potential threats, assessing the significance of associated risks, and implementing mitigation strategies.

  • Risks assessments performed

    The company performs risk assessments at least annually. This process includes identifying threats and changes (environmental, regulatory, and technological) that may affect service commitments, formally assessing the related risks, and considering how potential fraud could impact the achievement of objectives.

  • Change management procedures enforced

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

Support

  • Security awareness training implemented

    Employees are required to complete security awareness training within 30 days of being hired and at least once a year thereafter.

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Incident response policies established

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

  • Risk management program established

    The company maintains a documented risk management program that provides guidance on identifying potential threats, assessing the significance of associated risks, and implementing mitigation strategies.

  • Change management procedures enforced

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

  • Customer data retained

    The company retains customer transaction data for the duration of the customer account. Historical transaction data is not purged until the account is deleted.

Operation

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Risks assessments performed

    The company performs risk assessments at least annually. This process includes identifying threats and changes (environmental, regulatory, and technological) that may affect service commitments, formally assessing the related risks, and considering how potential fraud could impact the achievement of objectives.

  • Change management procedures enforced

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

Performance evaluation

  • Board oversight briefings conducted (SOC 2)

    Senior management briefs the board of directors, or an appropriate subcommittee, at least once a year on the company’s cybersecurity and privacy risk posture. The board offers guidance and feedback to management as necessary.

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Infrastructure performance monitored

    The company uses an infrastructure monitoring tool to track systems, infrastructure, and performance, generating alerts when predefined thresholds are reached.

  • Security controls evaluated

    The company conducts periodic technical and nontechnical evaluations, initially based on the HIPAA Security Rule, and subsequently in response to environmental or operational changes affecting the security of electronic Protected Health Information (ePHI), to determine whether its security policies and procedures continue to meet the requirements of the HIPAA Security Rule (Subpart C).

  • Audit controls implemented

    The company has implemented hardware, software, and procedural mechanisms to log and review activity within information systems that store or process electronic Protected Health Information (ePHI).

  • AI Compliance Integration

    Where a product incorporates an AI system and is subject both to the requirements of this Regulation and to the requirements of applicable Union harmonisation legislation, the provider shall be responsible for ensuring that the product complies in full with all applicable requirements under that Union harmonisation legislation. When ensuring that high-risk AI systems comply with the requirements set out in this Section, providers may, for the purpose of ensuring consistency, avoiding duplication, and minimising additional burdens, choose to integrate the relevant testing and reporting activities, as well as the information and documentation relating to the AI system, into existing documentation and procedures required under the applicable Union harmonisation legislation.

Improvement

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Nonconformity and corrective action

    When a nonconformity is identified, the organization: 1. Responds to the issue by: a) Taking action to control and correct it b) Addressing any resulting consequences 2. Assesses the need for action to prevent recurrence or occurrence elsewhere by: a) Reviewing the nonconformity b) Identifying its root causes c) Determining whether similar issues exist or could potentially arise 3. Implements necessary corrective actions 4. Evaluates the effectiveness of those actions 5. Updates the information security management system as needed Corrective actions are proportionate to the impact of the nonconformities. Documented information is retained to demonstrate: 1. The nature of the nonconformities and the actions taken 2. The results of any corrective actions

Organisational Controls

  • Roles and responsibilities specified

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

  • Security awareness training implemented

    Employees are required to complete security awareness training within 30 days of being hired and at least once a year thereafter.

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Incident response policies established

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

  • Third-party agreements established

    The company maintains written agreements with vendors and third parties, which include applicable confidentiality and privacy commitments.

  • Continuity and disaster recovery plans tested

    The company has a documented Business Continuity and Disaster Recovery (BC/DR) plan, which is tested at least once a year.

  • Risks assessments performed

    The company performs risk assessments at least annually. This process includes identifying threats and changes (environmental, regulatory, and technological) that may affect service commitments, formally assessing the related risks, and considering how potential fraud could impact the achievement of objectives.

  • Vendor management program established

    The company has a vendor management program in place that includes: 1. Critical third-party vendor inventory 2. Vendor security and privacy requirements 3. Review of critical third-party vendors at least annually

  • Access control procedures established

    The company’s access control policy outlines requirements for the following access control functions: 1. Adding new users 2. Modifying users 3. Removing user access

  • Change management procedures enforced

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

  • Production inventory maintained

    The company maintains a formal inventory of assets within the production environment.

  • Unique production database authentication enforced

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

  • Data classification policy established

    The company has a data classification policy to ensure confidential data is properly secured and accessible only to authorized personnel.

  • Production application access restricted

    System access is restricted to authorized users only.

  • Production OS access restricted

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

  • Access requests required

    The company ensures that access to in-scope system components is based on job role and function or requires a documented access request and manager approval before access is granted.

  • Access revoked upon termination

    The company uses termination checklists to ensure access for terminated employees is revoked within defined SLAs.

  • Asset disposal procedures utilized

    The company ensures electronic media containing confidential information is purged or destroyed following best practices, with certificates of destruction issued for each device.

  • Network firewalls utilized

    The company uses firewalls configured to block unauthorized access.

  • Vulnerability and system monitoring procedures established

    The company’s formal policies define requirements for the following IT and engineering functions: 1. Vulnerability management 2. System monitoring

  • Infrastructure performance monitored

    The company uses an infrastructure monitoring tool to track systems, infrastructure, and performance, generating alerts when predefined thresholds are reached.

  • Incident response plan tested

    The company tests its incident response plan at least once a year.

  • Customer data retained

    The company retains customer transaction data for the duration of the customer account. Historical transaction data is not purged until the account is deleted.

  • Legal personal information tracked

    The company logs, tracks, and maintains records of personal information disclosed for legal purposes in its designated tracking system for historical reference and audit purposes.

  • Private data shared upon request

    The company provides requested information, after verification, in a timely manner either in a portable electronic format or by mail, in compliance with applicable law.

  • Sanction policy applied

    The company enforces appropriate sanctions against workforce members who fail to comply with its security policies and procedures.

  • Security incidents identified and reported

    The company identifies and responds to suspected or known security incidents, mitigates harmful effects to the extent practicable, and documents the incidents along with their outcomes.

  • Contingency plan established

    The company has established and implements, as needed, policies and procedures for responding to emergencies or other events (such as fire, vandalism, system failure, or natural disaster) that may damage systems containing electronic Protected Health Information (ePHI).

  • Contingency operations established

    The company has established procedures, to be implemented when needed, that allow facility access during emergencies in order to support data restoration as outlined in the disaster recovery and emergency mode operations plans.

  • PII minimization

    The company ensures that data collection and processing are limited to what is required to fulfill the purposes explicitly defined in its documented data processing activities, supporting compliance with data minimization requirements.

  • Retention of PII

    The company retains personally identifiable information (PII) only for the duration necessary to fulfill the purposes for which it was collected, in alignment with applicable data retention policies.

  • Contracts with PII processors

    The company enters into a written agreement with each processor of personally identifiable information (PII), defining the processor’s responsibilities and required compliance with applicable data protection standards.

  • Breach policy and procedure

    The company establishes documented policies and procedures for responding to data breaches, which include defined notification processes to ensure timely communication to relevant stakeholders.

  • Identity management

    The organization manages identities throughout their entire lifecycle, from creation and use to modification and deactivation.

  • Managing information security in the ICT supply chain

    The organization defines and implements processes and procedures to manage information security risks within the ICT products and services supply chain.

  • Information security for use of cloud services

    The organization establishes processes for the acquisition, use, management, and exit of cloud services in alignment with its information security requirements.

  • ICT readiness for business continuity

    ICT readiness is planned, implemented, maintained, and tested in alignment with business continuity objectives and ICT continuity requirements.

  • Intellectual property rights

    The organization implements appropriate procedures to safeguard intellectual property rights.

  • Compliance with policies, rules and standards for information security

    The organization conducts regular reviews to ensure compliance with its information security policy, topic-specific policies, rules, and standards.

  • Threats and vulnerabilities regularly addressed

    For public-facing web applications, the company addresses new threats and vulnerabilities on an ongoing basis and protects these applications against known attacks by implementing one of the following methods: 1. Conducting manual or automated application vulnerability assessments that: a) Occur at least annually and after any changes b) Are performed by organizations specializing in application security c) Include all vulnerabilities d) Ensure that all identified vulnerabilities are corrected e) Include re-evaluation of the application following remediation 2. Deploying an automated technical solution, such as a web application firewall, that: a) Is positioned in front of public-facing web applications to detect and prevent attacks b) Is actively running and kept up to date c) Generates audit logs d) Is configured to either block detected web-based attacks or generate alerts that are promptly investigated

  • Information security policy reviewed annually

    The company reviews the security policy at least annually and updates it whenever there are changes to the environment.

  • System access restricted to authorized access only

    The organization shall limit system access exclusively to authorized users, processes operating on behalf of authorized users, and approved devices, including interconnected systems.

  • Unique accounts, services, and processes are in use

    The organization shall identify system users, processes operating on behalf of users, and devices.

  • Threat Intelligence Collection and Analysis

    The organization shall gather and evaluate threat intelligence to identify emerging risks and strengthen its defensive posture. Threat intelligence practices shall be maintained as documented information and assessed regularly to verify their effectiveness.

  • Including Information Security in the Business Continuity Management Process

    A managed program and process shall be developed and maintained for business continuity throughout the organization that addresses the information security requirements needed for the organization's business continuity.

  • AI Compliance Integration

    Where a product incorporates an AI system and is subject both to the requirements of this Regulation and to the requirements of applicable Union harmonisation legislation, the provider shall be responsible for ensuring that the product complies in full with all applicable requirements under that Union harmonisation legislation. When ensuring that high-risk AI systems comply with the requirements set out in this Section, providers may, for the purpose of ensuring consistency, avoiding duplication, and minimising additional burdens, choose to integrate the relevant testing and reporting activities, as well as the information and documentation relating to the AI system, into existing documentation and procedures required under the applicable Union harmonisation legislation.

  • System validation

    Persons who use closed systems to create, modify, maintain, or transmit electronic records shall validate those systems for accuracy, reliability, consistent intended performance, and the ability to detect invalid or altered records.

People Controls

  • Employee background checks performed

    The company conducts background screenings for all new hires.

  • Confidentiality Agreement acknowledged by contractors

    Contractors are required to sign a confidentiality agreement when their engagement begins.

  • Confidentiality Agreement acknowledged by employees

    Employees are required to sign a confidentiality agreement as part of the onboarding process.

  • Roles and responsibilities specified

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

  • Security awareness training implemented

    Employees are required to complete security awareness training within 30 days of being hired and at least once a year thereafter.

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Incident response policies established

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

  • Access control procedures established

    The company’s access control policy outlines requirements for the following access control functions: 1. Adding new users 2. Modifying users 3. Removing user access

  • Access revoked upon termination

    The company uses termination checklists to ensure access for terminated employees is revoked within defined SLAs.

  • MDM system utilized

    The company uses a mobile device management (MDM) system to centrally manage mobile devices that support the service.

  • Sanction policy applied

    The company enforces appropriate sanctions against workforce members who fail to comply with its security policies and procedures.

  • Security incidents identified and reported

    The company identifies and responds to suspected or known security incidents, mitigates harmful effects to the extent practicable, and documents the incidents along with their outcomes.

  • Compliance with policies, rules and standards for information security

    The organization conducts regular reviews to ensure compliance with its information security policy, topic-specific policies, rules, and standards.

Physical Controls

  • Continuity and disaster recovery plans tested

    The company has a documented Business Continuity and Disaster Recovery (BC/DR) plan, which is tested at least once a year.

  • Access control procedures established

    The company’s access control policy outlines requirements for the following access control functions: 1. Adding new users 2. Modifying users 3. Removing user access

  • Production inventory maintained

    The company maintains a formal inventory of assets within the production environment.

  • Data classification policy established

    The company has a data classification policy to ensure confidential data is properly secured and accessible only to authorized personnel.

  • Data center access reviewed

    The company reviews data center access at least once a year.

  • Production data segmented

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

  • Intrusion detection system utilized

    The company uses an intrusion detection system to continuously monitor its network and detect potential security breaches early.

  • MDM system utilized

    The company uses a mobile device management (MDM) system to centrally manage mobile devices that support the service.

  • Production data backups conducted

    The company performs periodic backups of production data, storing the backups in a separate location from the production environment.

  • Environmental monitoring devices implemented

    The company uses environmental monitoring devices configured to automatically alert management in the event of environmental incidents.

  • Environmental security inspected

    The company conducts maintenance inspections of environmental security measures at its data centers at least once a year.

  • Contingency plan established

    The company has established and implements, as needed, policies and procedures for responding to emergencies or other events (such as fire, vandalism, system failure, or natural disaster) that may damage systems containing electronic Protected Health Information (ePHI).

  • Application and data criticality analyzed

    The company assesses the relative criticality of specific applications and data to support the development and execution of other contingency plan components.

  • Maintenance records maintained

    The company has established policies and procedures to document all repairs and modifications to the physical components of its facilities that relate to security, including items such as hardware, walls, doors, and locks.

  • Equipment maintenance

    The organization ensures that equipment is properly maintained to support the availability, integrity, and confidentiality of information.

Technological Controls

  • Security policies established and reviewed

    The company’s information security policies and procedures are formally documented and reviewed at least once a year.

  • Third-party agreements established

    The company maintains written agreements with vendors and third parties, which include applicable confidentiality and privacy commitments.

  • Continuity and disaster recovery plans tested

    The company has a documented Business Continuity and Disaster Recovery (BC/DR) plan, which is tested at least once a year.

  • Configuration management system established

    The company has a configuration management procedure to ensure consistent deployment of system configurations across the environment.

  • Development lifecycle established

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

  • Access control procedures established

    The company’s access control policy outlines requirements for the following access control functions: 1. Adding new users 2. Modifying users 3. Removing user access

  • Change management procedures enforced

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

  • Backup processes established

    The company’s data backup policy defines the requirements for backing up and recovering customer data.

  • Production deployment access restricted

    The company restricts production change migrations to authorized personnel only.

  • Unique production database authentication enforced

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

  • Encryption key access restricted

    The company limits privileged access to encryption keys to authorized users who have a valid business need.

  • Data classification policy established

    The company has a data classification policy to ensure confidential data is properly secured and accessible only to authorized personnel.

  • Production application access restricted

    System access is restricted to authorized users only.

  • Production OS access restricted

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

  • Production network access restricted

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

  • Unique network system authentication enforced

    The company requires authentication to the production network to use unique usernames and passwords or authorized SSH keys.

  • Network segmentation implemented

    The company’s network is segmented to block unauthorized access to customer data.

  • Production data segmented

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

  • Intrusion detection system utilized

    The company uses an intrusion detection system to continuously monitor its network and detect potential security breaches early.

  • Network firewalls reviewed

    The company reviews firewall rulesets at least once a year, with required changes tracked to completion.

  • Network firewalls utilized

    The company uses firewalls configured to block unauthorized access.

  • Service infrastructure maintained

    The company patches infrastructure supporting the service as part of routine maintenance and in response to identified vulnerabilities to help ensure servers are hardened against security threats.

  • MDM system utilized

    The company uses a mobile device management (MDM) system to centrally manage mobile devices that support the service.

  • Infrastructure performance monitored

    The company uses an infrastructure monitoring tool to track systems, infrastructure, and performance, generating alerts when predefined thresholds are reached.

  • Database replication utilized

    The company’s databases are replicated in real time to a secondary data center, with alerts set up to notify administrators of any replication failures.

  • Production data backups conducted

    The company performs periodic backups of production data, storing the backups in a separate location from the production environment.

  • Production multi-availability zones established

    The company employs a multi-location strategy for production environments to enable operations to resume at alternate data centers if a facility becomes unavailable.

  • Customer transaction modifications restricted

    The company ensures that customer transaction data cannot be modified by either customers or administrators within the production application.

  • Data deletion requests handled

    The company validates deletion requests, and once confirmed, flags and deletes the requested information in accordance with applicable laws and regulations.

  • Contingency plan established

    The company has established and implements, as needed, policies and procedures for responding to emergencies or other events (such as fire, vandalism, system failure, or natural disaster) that may damage systems containing electronic Protected Health Information (ePHI).

  • Audit controls implemented

    The company has implemented hardware, software, and procedural mechanisms to log and review activity within information systems that store or process electronic Protected Health Information (ePHI).

  • PII de-identification and deletion at the end of processing

    The company deletes or de-identifies data when it is no longer required for the purposes for which it was originally collected or processed, in accordance with data retention and minimization principles.

  • Firewall and router configuration process

    The company establishes and enforces firewall and router configuration standards that include a documented process for approving and testing all network connections, as well as any changes to firewall and router configurations.

  • System audit trails enabled and active

    The company ensures that audit trails are enabled and active on all system components to record relevant security events.

  • Threats and vulnerabilities regularly addressed

    For public-facing web applications, the company addresses new threats and vulnerabilities on an ongoing basis and protects these applications against known attacks by implementing one of the following methods: 1. Conducting manual or automated application vulnerability assessments that: a) Occur at least annually and after any changes b) Are performed by organizations specializing in application security c) Include all vulnerabilities d) Ensure that all identified vulnerabilities are corrected e) Include re-evaluation of the application following remediation 2. Deploying an automated technical solution, such as a web application firewall, that: a) Is positioned in front of public-facing web applications to detect and prevent attacks b) Is actively running and kept up to date c) Generates audit logs d) Is configured to either block detected web-based attacks or generate alerts that are promptly investigated

  • Critical system review performed quarterly (SOC 2)

    For service providers, the company performs reviews at least quarterly to confirm personnel comply with security policies and operational procedures.

  • Use DNS filtering services

    The organization uses DNS filtering services on all end-user devices, including remote and on-premises assets, to block access to known malicious domains.

  • Maintain and enforce network-based URL filters

    The organization enforces and updates network-based URL filters to prevent enterprise assets from connecting to potentially malicious or unapproved websites. Implementations may include category-based filtering, reputation-based filtering, or block lists. Filters are enforced for all enterprise assets.

  • AI system requirements and specification

    The organization should specify and maintain documented requirements for new AI systems and for material enhancements to existing systems.

  • System access restricted to authorized access only

    The organization shall limit system access exclusively to authorized users, processes operating on behalf of authorized users, and approved devices, including interconnected systems.

  • Multi-factor authentication (MFA) used for all admin access

    The organization shall require multi-factor authentication for both local and network access to privileged accounts, and for network access to non-privileged accounts.

  • AI Compliance Integration

    Where a product incorporates an AI system and is subject both to the requirements of this Regulation and to the requirements of applicable Union harmonisation legislation, the provider shall be responsible for ensuring that the product complies in full with all applicable requirements under that Union harmonisation legislation. When ensuring that high-risk AI systems comply with the requirements set out in this Section, providers may, for the purpose of ensuring consistency, avoiding duplication, and minimising additional burdens, choose to integrate the relevant testing and reporting activities, as well as the information and documentation relating to the AI system, into existing documentation and procedures required under the applicable Union harmonisation legislation.

  • System validation

    Persons who use closed systems to create, modify, maintain, or transmit electronic records shall validate those systems for accuracy, reliability, consistent intended performance, and the ability to detect invalid or altered records.