pentesting

name	pentesting
description	Ethical penetration testing guidance with AI assistance. Use ONLY for authorized security testing, bug bounty programs, or systems you own. STRICT SAFETY GUIDELINES MUST BE FOLLOWED.

CRITICAL SAFETY WARNING

This skill MUST ONLY be used for:

• Systems you own or have explicit written permission to test
• Authorized bug bounty programs with clear scope
• Educational environments with proper authorization
• Security research with responsible disclosure

NEVER use this skill for:

• Unauthorized access to systems you don't own
• Testing systems without explicit permission
• Malicious activities or attacks
• Violating laws or regulations
• Bypassing security controls without authorization

Legal Consequences:

• Unauthorized access is illegal (Computer Fraud and Abuse Act, GDPR, etc.)
• Penalties include fines, imprisonment, and criminal records
• Civil liability for damages
• Professional consequences

Ethical Guidelines

Core Principles

1. Authorization First: Always obtain explicit written permission before testing
2. Scope Adherence: Only test within defined boundaries
3. Responsible Disclosure: Report vulnerabilities through proper channels
4. No Harm: Do not cause damage or disruption
5. Privacy Respect: Protect sensitive data encountered during testing
6. Legal Compliance: Follow all applicable laws and regulations

Authorization Requirements

• Written permission from system owner
• Clear scope definition (IPs, domains, systems)
• Testing window/timeframe
• Allowed testing methods
• Contact information for security team
• Rules of engagement

AI-Assisted Pentesting

When AI Can Help

• Generating test payloads (within scope)
• Analyzing code for vulnerabilities
• Creating documentation
• Suggesting testing methodologies
• Automating repetitive tasks
• Learning new techniques

When AI Should NOT Be Used

• To bypass authorization
• To generate exploits for unauthorized systems
• To automate attacks without oversight
• To obfuscate malicious activities
• To evade detection controls

AI Safety Protocols

1. Verify Authorization: AI must confirm authorization before suggesting any testing
2. Scope Validation: AI must check if target is within authorized scope
3. Harm Assessment: AI must assess potential impact before suggesting actions
4. Legal Compliance: AI must ensure suggested actions comply with laws
5. Human Oversight: All AI suggestions must be reviewed by authorized personnel

Testing Methodologies

OWASP Testing Guide

Follow OWASP Web Security Testing Guide (WSTG):

• Information Gathering
• Configuration Management
• Identity Management
• Authentication
• Authorization
• Session Management
• Input Validation
• Error Handling
• Data Protection
• Business Logic
• Client-Side Testing

PTES (Penetration Testing Execution Standard)

1. Pre-Engagement Interactions
2. Intelligence Gathering
3. Threat Modeling
4. Vulnerability Analysis
5. Exploitation
6. Post-Exploitation
7. Reporting

NIST SP 800-115

• Planning
• Discovery
• Attack
• Reporting

Common Vulnerability Types

Web Applications

• SQL Injection
• Cross-Site Scripting (XSS)
• Cross-Site Request Forgery (CSRF)
• Authentication Bypass
• Authorization Flaws
• Insecure Direct Object References
• Security Misconfiguration
• Sensitive Data Exposure
• Broken Access Control
• Server-Side Request Forgery (SSRF)

Network Security

• Unencrypted Services
• Default Credentials
• Misconfigured Firewalls
• Outdated Software
• Weak Authentication
• Network Sniffing Vulnerabilities

AI/ML Systems

• Prompt Injection
• Model Inversion
• Data Poisoning
• Membership Inference
• Adversarial Examples
• Model Extraction

Testing Tools (Use Only With Authorization)

Reconnaissance

# Nmap - Network scanning (AUTHORIZED ONLY)
nmap -sV -sC target.com

# Nikto - Web server scanning (AUTHORIZED ONLY)
nikto -h target.com

# WhatWeb - Technology identification (AUTHORIZED ONLY)
whatweb target.com

Vulnerability Scanning

# Nessus - Vulnerability scanner (AUTHORIZED ONLY)
# Requires license and authorization

# OpenVAS - Open source scanner (AUTHORIZED ONLY)
# Requires authorization

# OWASP ZAP - Web application scanner (AUTHORIZED ONLY)
zap-cli quick-scan --self-contained http://target.com

Web Testing

# SQLMap - SQL injection testing (AUTHORIZED ONLY)
# Only on systems you own or have explicit permission

# Burp Suite - Web application testing (AUTHORIZED ONLY)
# Only on authorized targets

Responsible Disclosure

Disclosure Process

1. Report to Vendor: Contact security team through proper channels
2. Provide Details: Include vulnerability description, impact, reproduction steps
3. Allow Time: Give vendor reasonable time to fix (typically 90 days)
4. Coordinate: Coordinate disclosure timeline with vendor
5. Public Disclosure: Only after fix is deployed or deadline expires

Bug Bounty Programs

• Read program rules carefully
• Understand scope and exclusions
• Follow reporting guidelines
• Don't exceed testing boundaries
• Don't test on production data
• Report through official channels

Sample Disclosure Template

Subject: Security Vulnerability Report - [Vulnerability Name]

Dear Security Team,

I have discovered a security vulnerability in [System Name].

Vulnerability: [Brief description]
Severity: [Critical/High/Medium/Low]
Impact: [Potential impact]
Affected System: [URL/IP]
Steps to Reproduce:
1. [Step 1]
2. [Step 2]
3. [Step 3]

Suggested Fix: [Recommendation]

I discovered this vulnerability while [context: authorized testing/bug bounty program].

Please let me know if you need additional information.

Regards,
[Your Name]
[Contact Information]

Safety Checklists

Before Testing

• Written authorization obtained
• Scope clearly defined
• Legal review completed
• Testing environment prepared
• Backup systems available
• Emergency contact established
• Testing timeframe agreed
• Rules of engagement documented

During Testing

• Stay within authorized scope
• Document all findings
• Avoid production data
• Minimize system impact
• Stop if unexpected issues arise
• Maintain communication with owner
• Respect rate limits
• Don't exploit beyond proof of concept

After Testing

• Secure all test data
• Delete sensitive information
• Provide detailed report
• Recommend remediation steps
• Assist with validation
• Follow disclosure timeline
• Document lessons learned

AI Safety Guidelines for Pentesting

What AI Should Do

• Ask for authorization before suggesting tests
• Verify scope before generating payloads
• Suggest defensive measures
• Provide educational explanations
• Recommend responsible disclosure
• Flag potential legal issues
• Encourage ethical behavior

What AI Should NOT Do

• Generate exploits for unauthorized targets
• Suggest bypassing authorization
• Provide instructions for illegal activities
• Obfuscate malicious intent
• Automate attacks without oversight
• Ignore scope boundaries
• Minimize legal consequences

AI Response Protocol

When asked about pentesting:

1. Verify Authorization: Ask "Do you have authorization to test this system?"
2. Check Scope: Ask "What is the authorized scope?"
3. Assess Intent: Determine if request is legitimate
4. Provide Guidance: If authorized, provide ethical guidance
5. Refuse Malicious Requests: If unauthorized, refuse and explain why

Legal Framework

Key Laws

• CFAA (US): Computer Fraud and Abuse Act
• GDPR (EU): General Data Protection Regulation
• CCPA (California): California Consumer Privacy Act
• Computer Misuse Act (UK): UK computer security law
• Various Country Laws: Local cybersecurity laws

Penalties

• Fines up to millions of dollars
• Imprisonment (up to 20+ years)
• Civil liability
• Professional license revocation
• Employment termination
• Criminal record

Educational Resources

Certifications

• CEH (Certified Ethical Hacker)
• OSCP (Offensive Security Certified Professional)
• CISSP (Certified Information Systems Security Professional)
• PTES (Penetration Testing Execution Standard)
• OWASP certifications

Documentation

• OWASP Web Security Testing Guide
• NIST SP 800-115
• PTES Technical Guidelines
• OSSTMM (Open Source Security Testing Methodology)

Communities

• OWASP Foundation
• Bug bounty platforms (HackerOne, Bugcrowd)
• Local security meetups
• Security conferences (DEF CON, Black Hat)

Common Gotchas

Authorization Issues

• Assuming implied permission
• Testing beyond agreed scope
• Not getting written permission
• Ignoring time restrictions
• Testing production systems without approval

Legal Issues

• Not understanding local laws
• Violating data protection laws
• Testing across jurisdictions
• Not considering international laws
• Ignoring terms of service

Ethical Issues

• Causing disruption
• Accessing sensitive data unnecessarily
• Not reporting vulnerabilities responsibly
• Public disclosure before vendor notification
• Using discovered vulnerabilities maliciously

Scripts (Use Only With Authorization)

Basic Security Check (Educational)

#!/usr/bin/env python3
"""
Educational script to demonstrate security concepts.
ONLY RUN ON SYSTEMS YOU OWN OR HAVE EXPLICIT PERMISSION.
"""

def check_security_headers(url):
    """
    Check for security headers (educational example).
    Requires authorization to test target.
    """
    import requests
    
    print("WARNING: Only run on authorized targets")
    response = requests.get(url)
    
    headers = {
        'X-Frame-Options': response.headers.get('X-Frame-Options'),
        'X-Content-Type-Options': response.headers.get('X-Content-Type-Options'),
        'Strict-Transport-Security': response.headers.get('Strict-Transport-Security'),
        'Content-Security-Policy': response.headers.get('Content-Security-Policy'),
    }
    
    return headers

# Usage (ONLY with authorization):
# check_security_headers('https://example.com')

Vulnerability Scanner Template

#!/usr/bin/env python3
"""
Template for authorized vulnerability scanning.
MUST HAVE EXPLICIT WRITTEN AUTHORIZATION.
"""

def authorized_scan(target, authorization_document):
    """
    Scan target only with proper authorization.
    """
    # Verify authorization
    if not authorization_document:
        raise Exception("Authorization required")
    
    # Check scope
    # Implement scope validation
    
    # Perform scan within scope
    # Document findings
    
    # Report to authorized contact
    pass

When to Use This Skill

Appropriate Use:

• Learning about security concepts
• Understanding vulnerabilities
• Preparing for authorized testing
• Bug bounty program participation
• Security research with proper oversight
• Building secure applications

Inappropriate Use:

• Testing systems without permission
• Learning to hack unauthorized targets
• Bypassing security controls
• Attacking systems
• Stealing data
• Causing harm

Reporting Security Issues

If you discover a security issue:

1. Stop testing immediately
2. Document the finding
3. Report through responsible disclosure
4. Do not exploit further
5. Do not disclose publicly
6. Follow vendor's disclosure policy

Resources

• OWASP: https://owasp.org
• HackerOne: https://hackerone.com
• Bugcrowd: https://bugcrowd.com
• NIST Cybersecurity: https://csrc.nist.gov
• CERT Coordination Center: https://cert.org

Final Reminder

Ethical hacking is about improving security, not causing harm. Always obtain authorization before testing. Follow responsible disclosure practices. Respect privacy and legal boundaries. Use your skills for good.