Control mapping
Where each questionnaire section finds its answer.
Questionnaire domains mapped to ARRTECH controls
A useful mapping connects a requirement to a function, its owner and the evidence of operation. Use the domains below to guide review of the proposed configuration.
Domains
Access control.
Roles in each tenant decide who can use each log source and feature. See Product security, Scoped roles.
Secrets management.
Integration credentials and agent identities need access limited to their work. See Product security, One vault and Separate keys.
Logging and monitoring.
The console records every login, search and configuration change, and ARRTECH SIEM signs every log. See Audit evidence.
Software integrity.
Agents are code-signed, and the console manages the certificates. See Product security, Signed agents.
Data location.
Data residency lists where each product runs and every outbound connection.
AI governance.
AI system inventory lists what each AI component does. Cyberdroid AI Detection is available now to select organizations, and Investigation is in early access.
Verify
Local records.
Retained configuration and activity records help reviewers examine the controls in the actual deployment.
Limits
Unlisted domains.
Use the mapping alongside the organization’s wider security program. A questionnaire response should identify the responsible owner and supporting evidence for each relevant domain.
Page scope.
These summaries explain the product’s role. The proposed deployment identifies the enabled functions, supported configuration and operating responsibilities.
