Q-CTRL security & compliance
An overview of Q-CTRL's security posture — compliance, penetration testing, subprocessors, and data handling — verified on SOC2C (Listed).
SOC 2 statusSOC 2 · Listed
FrameworksGDPR, NIST CSF
Penetration testNot listed
SubprocessorsNot listed
HostingNot listed
Trust centerView
Security questions about Q-CTRL
- Is Q-CTRL secure?
- Security isn't a single yes/no, but Q-CTRL is SOC 2 compliant and holds GDPR, NIST CSF. SOC2C verifies its compliance posture and shows how strongly each fact is proven.
- Does Q-CTRL have a bug bounty or vulnerability disclosure program?
- Q-CTRL hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@q-ctrl.com or via a /security page.
- Who are Q-CTRL's subprocessors?
- Q-CTRL's subprocessors aren't listed on SOC2C yet. The company can add them so buyers can assess fourth-party risk.
- Where does Q-CTRL host or store data?
- Q-CTRL's hosting and data-residency details aren't listed on SOC2C yet. The company can add where it hosts (AWS, GCP, Azure) and which data it handles.
- Where is Q-CTRL's trust center or security page?
- Q-CTRL's trust center is at https://trust.q-ctrl.com. Its verified SOC 2 status, frameworks, and documents are summarized on its SOC2C profile.