Glossary · Security, trust and compliance
Vulnerability disclosure
The policy and channel for reporting a suspected security vulnerability in REAP: security@reapnet.ai, acknowledgment within two business days, and /.well-known/security.txt.
More in security, trust and compliance
- Audit scope
- CSA STAR, CAIQ and SIG
- CVE (Common Vulnerabilities and Exposures)
- Data processing agreement (DPA)
- Encryption in transit and at rest
- GDPR, UK GDPR and CCPA/CPRA
- HIPAA and PHI
- IAM (identity and access management)
- ISO/IEC 27001 and 42001
- Key management service (KMS)
- Lateral movement
- Multi-factor authentication (MFA)
- NERC CIP
- NIST Cybersecurity Framework (CSF)
- OWASP and ASVS
- PCI DSS
- Penetration test
- SAML and OIDC (single sign-on protocols)
- Secure software development (SSDF) and SBOM
- Security packet
- security.txt
- Server-side request forgery (SSRF)
- SOC 2 Type I and Type II
- SOC 2 Type II
- Subprocessor
- Trust Center
Bring us your last P1.
Keep the root cause to yourself; in a 30-minute session we walk through how REAP would have investigated it, evidence first. The replay on your own network happens inside the proof of value.