document-qa-system / data /sample_security_policy.txt
Varun2007's picture
Production Document Question Answering (DQA) ready for Hugging Face Spaces
d3d09d6
Raw History Blame Contribute Delete
3.78 kB
# Enterprise Cybersecurity & Information Governance Policy
## 1. Access Control and Identity Management (IAM)
All corporate systems and production cloud environments require mandatory multi-factor authentication (MFA) using FIDO2-compliant WebAuthn hardware security keys. SMS and time-based one-time password (TOTP) apps are prohibited for administrative and privileged infrastructure accounts.
Session timeouts are strictly enforced: inactive user console sessions automatically disconnect after 15 minutes of inactivity. Privileged command execution requires temporary elevated credentials approved via just-in-time (JIT) access approval workflows, with approvals expiring after 4 hours. All user access permissions are subject to formal quarterly access certifications reviewed by department directors.
## 2. Cryptographic and Encryption Standards
All sensitive data classified as Confidential or Restricted must be encrypted in transit and at rest:
- Data in transit: Mandatory Transport Layer Security (TLS) version 1.3. Ciphers supporting forward secrecy (ECDHE-RSA-AES128-GCM-SHA256 or better) are required. TLS 1.0, 1.1, and 1.2 are disabled on all external-facing load balancers.
- Data at rest: High-security storage volumes, S3 buckets, and relational databases must use Advanced Encryption Standard (AES) with 256-bit keys (AES-256-GCM). Cryptographic keys are managed via AWS Key Management Service (KMS) or HashiCorp Vault. All master encryption keys must undergo automated cryptographic rotation every 90 days.
## 3. Incident Response and Declaration SLA
Cybersecurity incidents are categorized into three severity levels:
- Severity 0 (P0 - Critical): Active data breach or critical infrastructure compromise. Maximum declaration SLA is 5 minutes from initial detection. An incident war room is automatically created within 10 minutes, and the Incident Commander must brief executive leadership every 30 minutes. Comprehensive post-mortem analysis must be published within 72 hours.
- Severity 1 (P1 - High): Significant system degradation or isolated security compromise without data exfiltration. Declaration SLA is 15 minutes. Post-mortem must be completed within 5 business days.
- Severity 2 (P2 - Medium): Vulnerability with potential impact or policy violation. Remediation must occur within 14 calendar days.
## 4. Vulnerability Management and Remediation Timelines
Security vulnerabilities identified through static application security testing (SAST), dynamic testing (DAST), or penetration testing must be remediated based on Common Vulnerability Scoring System (CVSS v3.1) base scores:
- Critical Vulnerabilities (CVSS 9.0 - 10.0): Remediation SLA is 48 hours from discovery.
- High Vulnerabilities (CVSS 7.0 - 8.9): Remediation SLA is 14 calendar days.
- Medium Vulnerabilities (CVSS 4.0 - 6.9): Remediation SLA is 30 calendar days.
- Low Vulnerabilities (CVSS 0.1 - 3.9): Remediation SLA is 90 calendar days or next scheduled release.
Failure to patch Critical vulnerabilities within 48 hours triggers automated quarantine of the affected host or container instance by the Security Operations Center (SOC).
## 5. Employee Endpoint and Device Security
All corporate laptops and mobile workstations must run enterprise Mobile Device Management (MDM) software with active endpoint detection and response (EDR) sensors.
Full-disk encryption (FileVault for macOS, BitLocker for Windows) is non-negotiable and enforced via MDM configuration profiles. Remote wipe capability must remain active at all times. Employees are strictly prohibited from using jailbroken, rooted, or personally owned devices (BYOD) for accessing production customer data or corporate repositories. Any lost or stolen device must be reported to security@acme.corp within 2 hours.