Control catalog
Seed controls across all four supported frameworks. Tenants adopt frameworks at onboarding; adoption materializes these entries into their `controls` table.
SOC 233 controls
CC1.1Control environment — integrity and ethical valuesThe entity demonstrates a commitment to integrity and ethical values.
CC1.2Control environment - board independence and oversightThe board of directors demonstrates independence from management and exercises oversight of internal control.
CC1.3Control environment - structure, authority, and responsibilityManagement establishes structures, reporting lines, and appropriate authorities and responsibilities.
CC1.4Control environment - competenceThe entity demonstrates a commitment to attract, develop, and retain competent individuals.
CC1.5Control environment - accountabilityThe entity holds individuals accountable for their internal control responsibilities.
CC2.1Information quality — relevant information for internal controlThe entity obtains or generates and uses relevant, quality information to support the functioning of internal control.
CC2.2Information and communication - internal communicationThe entity internally communicates information necessary to support internal control.
CC2.3Information and communication - external communicationThe entity communicates with external parties about matters affecting internal control.
CC3.1Risk assessment - objectivesThe entity specifies objectives with sufficient clarity to enable risk identification and assessment.
CC3.2Risk assessment - identifies and analyzes risksThe entity identifies risks to the achievement of objectives and analyzes those risks as a basis for response.
CC3.3Risk assessment - fraud riskThe entity considers the potential for fraud when assessing risks to objectives.
CC3.4Risk assessment - significant changeThe entity identifies and assesses changes that could significantly affect internal control.
CC4.1Monitoring activities - ongoing and separate evaluationsThe entity selects, develops, and performs ongoing and separate evaluations to determine whether controls are present and functioning.
CC4.2Monitoring activities - evaluates and communicates deficienciesThe entity evaluates and communicates internal control deficiencies in a timely manner.
CC5.1Control activities - selects and develops control activitiesThe entity selects and develops control activities that help mitigate risks to objectives.
CC5.2Control activities — technology general controlsThe entity selects and develops general control activities over technology to support the achievement of objectives.
CC5.3Control activities - policies and proceduresThe entity deploys control activities through policies that establish expectations and procedures that put policies into action.
CC6.1Logical access — access controlsThe entity implements logical access security software, infrastructure, and architectures over protected information assets.
CC6.2Logical access - user registration and authorizationBefore issuing credentials, the entity authorizes and registers new internal and external users.
CC6.3Logical access - access modification and removalThe entity authorizes, modifies, or removes access based on changes in user roles or termination.
CC6.4Logical access - restricts physical accessThe entity restricts physical access to facilities and protected information assets.
CC6.5Logical access - protects against unauthorized accessThe entity prevents or detects unauthorized access to system resources.
CC6.6Logical access - protects against malicious softwareThe entity implements controls to prevent, detect, and act on malicious software.
CC6.7Logical access - data transmission and disposalThe entity restricts the transmission, movement, and disposal of information to authorized channels.
CC6.8Logical access - vulnerability managementThe entity implements controls to identify and manage vulnerabilities in infrastructure and software.
CC7.1System operations - detection proceduresThe entity uses detection and monitoring procedures to identify events that may indicate security incidents.
CC7.2System operations — monitoring and anomaly detectionThe entity monitors system components and the operation of controls to detect anomalies indicative of malicious acts, natural disasters, and errors.
CC7.3System operations - evaluates security eventsThe entity evaluates security events to determine whether they could or did result in system failure or unauthorized activity.
CC7.4System operations - incident responseThe entity responds to identified security incidents by executing response procedures.
CC7.5System operations - incident recoveryThe entity identifies, develops, and implements activities to recover from identified security incidents.
CC8.1Change management - manages system changesThe entity authorizes, designs, develops, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures.
CC9.1Risk mitigation - selects and develops risk responsesThe entity identifies, selects, and develops risk mitigation activities for business disruptions and vendor or third-party risks.
CC9.2Risk mitigation - third-party risk managementThe entity assesses and manages risks associated with vendors and business partners.
GDPR16 controls
Art. 5Principles relating to processing of personal dataPersonal data must be processed lawfully, fairly, transparently, for specified purposes, with data minimisation, accuracy, storage limitation, integrity, confidentiality, and accountability.
Art. 6Lawfulness of processingProcessing is only lawful if at least one of the six lawful bases applies.
Art. 7Conditions for consentWhere processing is based on consent, the controller must be able to demonstrate valid consent and make withdrawal as easy as giving consent.
Art. 13Information to be provided where data is collected from the subjectControllers must provide transparent information at the point of collection, including identity, purposes, legal basis, retention, and rights.
Art. 15Right of accessData subjects have the right to obtain confirmation of processing and a copy of their personal data.
Art. 17Right to erasureData subjects have the right to request erasure of personal data in defined circumstances, including withdrawn consent, objection, unlawful processing, or expired purpose.
Art. 20Right to data portabilityData subjects have the right to receive personal data they provided in a structured, commonly used, machine-readable format and transmit it to another controller.
Art. 25Data protection by design and by defaultControllers must implement appropriate technical and organisational measures that embed data protection principles and default to only necessary processing.
Art. 28Processor obligationsControllers may use only processors providing sufficient guarantees, and processing must be governed by a contract with required data protection terms.
Art. 30Records of processing activitiesControllers and processors must maintain a written record of processing activities, including purposes, categories of data, and recipients.
Art. 32Security of processingControllers and processors must implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk.
Art. 33Notification of a personal data breach to the supervisory authorityPersonal data breaches must be reported to the supervisory authority within 72 hours of awareness, unless the breach is unlikely to result in a risk to rights and freedoms.
Art. 35Data protection impact assessmentWhere processing is likely to result in high risk to individuals, the controller must assess necessity, proportionality, risks, and risk mitigation before processing.
Art. 37Designation of the data protection officerControllers and processors must designate a data protection officer where required, including certain public authority, large-scale monitoring, or special-category processing contexts.
Art. 38Position of the data protection officerThe data protection officer must be properly involved, supported, independent in duties, reachable by data subjects, and bound by confidentiality.
Art. 39Tasks of the data protection officerThe data protection officer informs and advises, monitors compliance, advises on DPIAs, cooperates with supervisory authorities, and acts as a contact point.
EU AI Act12 controls
Art. 5Prohibited AI practicesSubliminal manipulation, exploitation of vulnerabilities, social scoring by public authorities, untargeted facial image scraping, emotion recognition in workplaces/schools, biometric categorisation on sensitive traits, and real-time remote biometric identification in public spaces (with narrow exceptions).
Art. 9Risk management systemHigh-risk AI providers must establish, implement, document, and maintain a risk management system throughout the system's lifecycle.
Art. 10Data and data governanceTraining, validation, and testing data sets must meet quality criteria including relevance, representativeness, and absence of errors, and must be examined for bias.
Art. 11Technical documentationHigh-risk AI providers must prepare technical documentation before placing a system on the market and keep it up to date to demonstrate compliance.
Art. 12Record-keepingHigh-risk AI systems must enable automatic recording of events over their lifetime to support traceability, monitoring, and incident investigation.
Art. 13Transparency and provision of information to deployersHigh-risk AI systems must be accompanied by instructions for use containing concise, accurate, and clear information relevant to deployers.
Art. 14Human oversightHigh-risk AI systems must be designed to be effectively overseen by humans, with measures proportionate to risk.
Art. 15Accuracy, robustness, and cybersecurityHigh-risk AI systems must be designed and developed to achieve appropriate accuracy, robustness, and cybersecurity throughout their lifecycle.
Art. 16Obligations of providers of high-risk AI systemsProviders of high-risk AI systems must ensure compliance, maintain quality management, keep documentation and logs, conduct conformity assessment, and take corrective action where needed.
Art. 26Obligations of deployers of high-risk AI systemsDeployers of high-risk AI systems must use systems according to instructions, ensure human oversight, monitor operation, retain logs where required, and report serious incidents.
Art. 50Transparency for certain AI systemsUsers must be informed when interacting with an AI system. Deepfakes and AI-generated text on matters of public interest must be labelled.
Art. 72Post-market monitoring by providersProviders of high-risk AI systems must establish a post-market monitoring system to collect, document, and analyze performance and compliance data after deployment.
ISO 2700116 controls
A.5.1Policies for information securityInformation security policy and topic-specific policies must be defined, approved by management, published, and reviewed.
A.5.7Threat intelligenceInformation relating to threats must be collected and analyzed to produce actionable threat intelligence.
A.5.8Information security in project managementInformation security must be integrated into project management practices for all projects.
A.5.23Information security for use of cloud servicesProcesses for acquisition, use, management, and exit from cloud services must address information security risks.
A.6.1ScreeningBackground verification checks must be carried out on candidates before joining and on an ongoing basis where appropriate.
A.6.2Terms and conditions of employmentEmployment agreements must state personnel responsibilities for information security.
A.6.3Information security awareness, education, and trainingPersonnel and relevant interested parties must receive appropriate information security awareness, education, and training.
A.6.8Information security event reportingPersonnel must be provided with a mechanism to report observed or suspected information security events promptly.
A.7.1Physical security perimetersSecurity perimeters must be defined and used to protect areas containing information and associated assets.
A.7.2Physical entry controlsSecure areas must be protected by appropriate entry controls and access points.
A.7.4Physical security monitoringPremises must be continuously monitored for unauthorized physical access.
A.7.8Equipment siting and protectionEquipment must be sited and protected to reduce risks from environmental threats and unauthorized access.
A.8.2Privileged access rightsThe allocation and use of privileged access rights must be restricted and managed.
A.8.5Secure authenticationSecure authentication technologies and procedures must be implemented based on access restrictions and the information classification.
A.8.16Monitoring activitiesNetworks, systems, and applications must be monitored for anomalous behaviour, with appropriate actions taken to evaluate potential security incidents.
A.8.24Use of cryptographyRules for effective use of cryptography, including cryptographic key management, must be defined and implemented.