CSG CYBER DEFENSE EDUCATION & RESEARCH FOUNDATION
CSG CYBER DEFENSE EDUCATION & RESEARCH FOUNDATION
Casual verbal remarks ("go ahead and test our site") or messages from junior staff carry zero evidentiary weight. If a SOC alert triggers a police cyber-cell investigation under IT Act Sections 43 & 66, undocumented verbal assurances cannot establish corporate owner consent or define allowed testing boundaries.
Written authorization to test System A never automatically extends to connected System B, partner APIs, VPN peers, or multi-tenant cloud services. Crossing a network bridge into uncontracted third-party infrastructure constitutes unauthorized intrusion.
Creates verifiable documentary proof of owner consent prior to sending a single probe packet.
Legal names of both Client and Testing Entity, effective dates, corporate registration/CIN, and explicit grant of conditional testing authority.
Confirms the contracting client actually owns or holds legal authority over every target domain and IP address listed.
Exact FQDNs, IPv4/IPv6 CIDR blocks, cloud account IDs, and confirmation that hosting providers (AWS/Azure/GCP) permit testing under tenant rules.
Ensures the person signing the permission document possesses legal corporate capacity to expose company systems to security testing.
Full legal name, corporate title (e.g., CISO, CTO, CIO, Managing Director, or Authorized Legal Counsel), corporate email, and dated signature.
Defines both what may be attacked and the exact tools/vectors that remain strictly forbidden.
Enumerated in-scope endpoints; permitted techniques (e.g. OWASP Top 10 manual audit, authenticated testing); explicitly excluded techniques (DoS, phishing, physical entry, production data modification).
Synchronizes testing windows with SOC monitoring and ensures an instant kill-switch contact exists if production instability occurs.
Exact Start/End dates, permitted daily hours (IST), source testing IPs for SOC whitelisting, and 24x7 phone numbers for Primary & Secondary Client Emergency POCs.
Governs how discovered secrets, personal data, and final vulnerability reports must be safeguarded, escalated, and sanitized.
Stop-work rule upon encountering PII, encrypted report delivery method (PGP/AES-256), critical vulnerability escalation SLA (e.g. 2 hours), and post-test evidence destruction timelines.
CSG Cyber School Engagement Authorization Curriculum • Standard SEC-LAW-205
Sample permission documents and checklists on this page are strictly educational templates for legal awareness and NOT individualized legal advice. Actual engagement agreements must be reviewed by qualified legal counsel and executed by authorized corporate officers prior to testing.