CERRIX Documentation
  • Introduction to CERRIX
  • CERRIX Functionalities
    • Getting Started
    • Using the Dashboard
    • Module Overview
      • Risks
        • AI Risk Description Refinement
        • Budget-based Risk Scoring
      • Controls
        • AI Control Description Refinement
      • Control Advanced Effectiveness Testing
        • Control Advanced Effectiveness Testing Video's
      • Incidents
        • Incidents Standing Data & Emails
        • Creating a New Incident
        • Incidents Workflow
        • Incidents Workspace
        • Incidents Roles & Rights
        • Incidents: Known Issues & Future Improvements
      • Events
      • Business Improvement Management
        • Measures of Improvement (MoIs)
          • Working with MoIs (Measures of Improvement)
        • Findings Report
      • Data Management
      • Third Party Management
      • Tasks & Control Execution
      • Key Risk Indicators (KRI's)
  • Admin Settings
    • External Connections
    • AI Settings
    • Authentication & User Provisioning
  • API Documentation
  • Best Practices & Guides
    • Control Design & Implementation, Execution & Effectiveness Testing: What's the Difference?
    • CERRIX AI FAQ
  • Implementation Guide
  • Import Templates
  • About CERRIX
    • Getting Support
    • Release Notes
    • Release Planning
    • Product Strategy & Roadmap
    • Heavy & Light Users
  • Compliance
    • Strategic Information Security Policy
    • ISO 27001
    • ISAE 3402 Type II
    • Privacy / GDPR
    • Security Statement
    • FSQS Certificate
Powered by GitBook
On this page
  • Steps to Set Up External Connection:
  • Requesting data through the API calls
  • Request the Export
  • Retrieve the Export Results
  • Request the export for Get Evidence Document
  • Logging
Export as PDF
  1. Admin Settings

External Connections

PreviousAdmin SettingsNextAI Settings

Last updated 1 month ago

CERRIX enables secure, controlled sharing of control test information and evidence through the External Connections module. This feature is especially useful for auditors or third parties who require direct access to relevant control data and documentation.

Steps to Set Up External Connection:

Navigate to the Administration Controls menu.

Click on External Connections.

Click on Add.

Fill in the following fields:

Name

Enter a name for the external connection.

Description (optional)

Provide a brief description of the external connection.

Assurance Employee (optional)

Select the person responsible for the external connection.

Click Next

Provide the following details:

Expiration Date

Specify the date until which the API can be accessed (maximum: 1 year from today).

IP Restriction

Enter the IP address from which the API can be accessed. Only API requests from these IP addresses will be accepted.

Click Next

Select the controls that can be queried through the API.

Click Next

From the dropdown menu, select Effectiveness under Testplan type.

Specify the Start Date and End Date for the testplans from the controls that may be queried through the API.

Click Next

Click Complete

Your API key and secret are now displayed on the screen. Ensure you store them securely, as they won't be shown again.

Requesting data through the API calls

Use your new API credentials to export control data. You can use any API tool (e.g., Postman) or your terminal. In the example below, we will use Postman.

Request the Export

Steps to Set Up ControlTestInformation:

  • Open Postman: Start the Postman application on your computer.

  • Create a New Request:

Click on the '+' icon or 'Create a request' to create a new request tab.

  • Set the HTTP Method:

From the dropdown menu next to the URL input bar, select the POST method.

  • Enter the URL:

Input the Base URL followed by the Routing path.

The Base URL is always composed of the environment URL followed by "/api,"

Fill in the URL as:

https://<your-environment>.cerrix.com/api/thirdpartyassurance/requestexport

  • Add the following query Params:

Key
Value

controlids

Enter the control ID in format “00000001”.

Add multiple controls by adding a semicolon ";" between the control IDs

testplantypes

Enter “Effectiveness”

testplanperiodstart

Enter the Start Date from the Period in format “2022-01-01”

testplanperiodend

Enter the End Date from the Period in format “2022-12-31”

  • Set up the Authorization.

    • Select the “Basic Auth” type.

    • Fill in the API key and secret as provided in the earlier step.

  1. Press "Send"

  2. A Request ID will be retrieved from the API call. Save this Request ID.

Retrieve the Export Results

  • Create a New Request:

Click on the '+' icon or 'Create a request' to create a new request tab.

  • Set the HTTP Method:

From the dropdown menu next to the URL input bar, select the GET method.

  • Enter the URL:

Input the Base URL followed by the Routing path.

The Base URL is always composed of the environment URL followed by "/api,"

Fill in the URL as:

https://<your-environment>.cerrix.com/api/thirdpartyassurance/getresults/<requestId>

  1. Fill in the 'requestId' field with the Request ID received through the previous API call.

  2. Set up the Authorization.

    1. Select the “Basic Auth” type.

    2. Fill in the API key and secret as provided in the earlier step.

  3. Press "Send"

  4. The API will respond with a JSON file.

Here's a sample response containing all information related to the control:

{
    "Status": "Data is ready",
    "Controls": [
        {
            "ControlIdentifier": "00000106",
            "ControlName": "User Acceptance Testing",
            "ControlDescription": "After the software change has been made based on the approved functional design, it is subject to a User Acceptance Testing process.",
            "ControlFrequency": "On Event",
            "KeyControl": true,
            "RequiresMonitoring": true,
            "ControlExecution": "Manual execution",
            "AspectIC": "Process controls",
            "MitigatedRisks": "Business Disruption due to implemented changes that are unsupported by ADHB requirements;Data in component banker can be filled in incorrectly",
            "RelatedOrganization": "Demo Organization\\Group Mortgages\\Operating companies\\Mortgages The Netherlands\\CFRO\\IT",
            "RelatedBusinessDimensions": [
                "Processes\\Supporting processes\\IT\\5 Regular Change Management"
            ],
            "RelatedFrameworkDimensions": [],
            "TestPeriods": [
                {
                    "TestPeriodName": "2024",
                    "TestPeriodScore": null,
                    "TestPeriodStartDate": "2024-01-01T00:00:00Z",
                    "TestPeriodEndDate": "2024-12-31T00:00:00Z",
                    "TestPlans": [
                        {
                            "TestPlanName": "2024",
                            "TestPlanStatus": "Waiting for evidence",
                            "TestPlanStartDate": "2024-01-01T00:00:00Z",
                            "TestPlanEndDate": "2024-12-31T00:00:00Z",
                            "SampleMethod": "One sample",
                            "ReasonForManualGeneration": "",
                            "SampleType": "Default",
                            "TestSample": 0,
                            "TestPopulation": 0,
                            "SourceDocumentUploader": "",
                            "DueDateSourceDocumentUploader": "0001-01-01T00:00:00Z",
                            "EvidenceUploaders": [
                                "Doe, John"
                            ],
                            "DueDateEvidenceUploader": "2025-01-01T00:00:00Z",
                            "Testers": [
                                "Doe, John"
                            ],
                            "DueDateTester": "2025-01-01T00:00:00Z",
                            "Reviewers": [
                                "Stas, Dart"
                            ],
                            "DueDateReviewer": "2025-01-01T00:00:00Z",
                            "LinkedStandard": "ISAE3402",
                            "QualityAspects": "Accuracy;Completeness;In Time",
                            "TestNorm": "",
                            "TestedBy": null,
                            "OverallScoreTester": null,
                            "CommentTester": null,
                            "DateTesterTested": "0001-01-01T00:00:00Z",
                            "ReviewedBy": null,
                            "OverallScoreReviewer": null,
                            "CommentReviewer": null,
                            "DateReviewerTested": "0001-01-01T00:00:00Z",
                            "TestSamples": [],
                            "SourceDocuments": []
                        }
                    ]
                }
            ]
        }
    ]
}

Request the export for Get Evidence Document

  • Create a New Request:

Click on the '+' icon or 'Create a request' to create a new request tab.

  • Set the HTTP Method:

From the dropdown menu next to the URL input bar, select the GET method.

  • Enter the URL:

Input the Base URL followed by the Routing path.

The Base URL is always composed of the environment URL followed by "/api,"

Fill in the URL as:

https://<your-environment>.cerrix.com/api/thirdpartyassurance/getevidencedocument/<requestId>

  • Add the following query Params:

Key
Value

controlidentifier

Enter the control ID in format “00000001”

documentid

Locate the Document ID within the JSON file received with the Export Results API call. This ID can be found within the SourceDocuments, SampleDocuments, or StepDocuments sections.

  • Fill in the 'requestId' field with the Request ID received in the first API call.

  • Set up the Authorization.

    • Select the “Basic Auth” type.

    • Fill in the API key and secret as provided in the earlier step.

  • Press "Send"

  • The document will be received as a binary stream from the API.

Logging

CERRIX logs all API calls made for external connections. This ensures users always have an overview of the requested APIs and their respective timestamps. Furthermore, it provides insight into the specific controls that were requested.

  • Navigate to the Administration Controls menu.

  • Click on Third Party Assurance.

On this page you can find an overview of all Third Party Assurance connections.

For each connection, you can access a log of which controls were accessed.

For routing to Control Test Information, please use the following path:

For routing to Get Result, please use the following path:

For routing to Get Evidence Document, please use the following path: