SOC2C

QAble Testlab security & compliance

An overview of QAble Testlab's security posture — compliance, penetration testing, subprocessors, and data handling — verified on SOC2C (Domain Verified).

SOC 2 statusSOC 2 · Domain Verified
FrameworksNot listed
Penetration testNot listed
SubprocessorsNot listed
HostingNot listed
Trust centerNot listed

Security questions about QAble Testlab

Is QAble Testlab secure?
Security isn't a single yes/no, but QAble Testlab is SOC 2 compliant. SOC2C verifies its compliance posture and shows how strongly each fact is proven.
Does QAble Testlab have a bug bounty or vulnerability disclosure program?
QAble Testlab hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@qable.io or via a /security page.
Who are QAble Testlab's subprocessors?
QAble Testlab's subprocessors aren't listed on SOC2C yet. The company can add them so buyers can assess fourth-party risk.
Where does QAble Testlab host or store data?
QAble Testlab'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 QAble Testlab's trust center or security page?
QAble Testlab hasn't linked a public trust center on SOC2C yet. Its SOC 2 status and frameworks are summarized on its SOC2C profile.

See QAble Testlab's full SOC 2 profile →