testcengiz

testcengiz

Trust Center

Default trust for organization

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

  • 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.

Communication and Information

  • 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.

  • Security policies established and reviewed

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

Monitoring Activities

  • 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

  • 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.

  • Security policies established and reviewed

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

  • Operational system checks

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

Logical and Physical Access Controls

  • 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.

  • 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.

  • System access limitation

    System access shall be restricted to authorized individuals.

  • 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.

System Operations

  • 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).

Change Management

  • 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

  • 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).

  • 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

Additional Criteria for Availability

  • 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).

  • 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.

  • 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

  • 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.

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.

  • 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.