Audits
Create a custom control for an audit
Create a custom control for an audit.
This endpoint supports classic audits only. Audits that use information request lists (IRL) are not supported and return a 422 error.
Rate limit: 10 requests / minute.
POST
TypeScript
Authorizations
Body
application/json
The category of the control. See the ControlDomain enum for possible values.
Available options:
ARTIFICIAL_&_AUTONOMOUS_TECHNOLOGY, ASSET_MANAGEMENT, BUSINESS_CONTINUITY_&_DISASTER_RECOVERY, CAPACITY_&_PERFORMANCE_PLANNING, CHANGE_MANAGEMENT, CLOUD_SECURITY, COMPLIANCE, CONFIGURATION_MANAGEMENT, CONTINUOUS_MONITORING, CRYPTOGRAPHIC_PROTECTIONS, DATA_CLASSIFICATION_&_HANDLING, EMBEDDED_TECHNOLOGY, ENDPOINT_SECURITY, HUMAN_RESOURCES_SECURITY, IDENTIFICATION_&_AUTHENTICATION, INCIDENT_RESPONSE, INFORMATION_ASSURANCE, MAINTENANCE, MOBILE_DEVICE_MANAGEMENT, NETWORK SECURITY, PHYSICAL_&_ENVIRONMENTAL_SECURITY, PRIVACY, PROJECT_&_RESOURCE MANAGEMENT, RISK_MANAGEMENT, SECURE_ENGINEERING_&_ARCHITECTURE, SECURITY_AWARENESS_&_TRAINING, SECURITY_OPERATIONS, SECURITY_&_PRIVACY_GOVERNANCE, TECHNOLOGY_DEVELOPMENT_&_ACQUISITION, THIRD-PARTY_MANAGEMENT, THREAT_MANAGEMENT, VULNERABILITY_&_PATCH_MANAGEMENT, WEB_SECURITY, ADMINISTRATIVE, PHYSICAL, TECHNICAL, BASIC, DERIVED The GDPR role of the control, which specifies whether the data is being "collected" or "processed". See the GdprRole enum for possible values. This field should only be included for controls that are to be mapped to the GDPR framework.
Available options:
BOTH, CONTROLLER, PROCESSOR Response
201 - application/json
Custom control created