• Supported Versions
• Reporting Vulnerabilities
• Security Guidelines
• Vulnerability Handling Policy
• Best Practices

This project maintains security updates for the following versions:

If you discover a security vulnerability in this project, please report it responsibly:

1. GitHub Issues (Preferred)

   • Open a new issue at: Security Issues
   • Use the title format: [SECURITY] Brief description

2. Direct Contact

   • Contact the project maintainer through GitHub

When reporting a vulnerability, please provide:

• Description: Clear explanation of the vulnerability
• Impact: What could an attacker do?
• Steps to Reproduce: How to trigger the vulnerability
• Environment: OS, Packet Tracer version
• Proof of Concept: Screenshots or detailed steps
• Suggested Fix (optional): If you have recommendations

• Acknowledgment: Within 48 hours
• Investigation: Within 7 days
• Resolution: Within 30 days (depending on severity)
• Public Disclosure: Coordinated with the reporter

When contributing to this project:

1. No Sensitive Information
   • Never include real IP addresses or credentials
   • Use documentation/example IP ranges (e.g., 10.0.0.0/8, 192.168.0.0/16)
   • Use placeholder passwords in configurations

! Good: Using documentation ranges
interface GigabitEthernet0/0
 ip address 192.168.1.1 255.255.255.0

! Bad: Using real network information
interface GigabitEthernet0/0
 ip address 203.0.113.50 255.255.255.252

2. Safe Configurations

   • Use example.com for domain names
   • Use generic hostnames (Router1, Switch1, etc.)
   • Avoid including SNMP community strings

3. File Safety

   • Scan files for malware before committing
   • Don't include executable files
   • Keep configurations clean and educational

When using this project:

1. Download from Official Source

   • Only clone from the official repository
   • Verify: https://github.com/H0NEYP0T-466/Computer-Network-Workbench.git

2. Review Configurations

   • Check configurations before applying to production
   • Understand what each command does
   • Use in isolated lab environments only

3. Safe Environment

   • Use Packet Tracer for testing (isolated environment)
   • Don't apply lab configs to production networks
   • Keep your Packet Tracer installation updated

We classify vulnerabilities by severity:

1. Triage

   • Validate the vulnerability
   • Assess severity and impact
   • Assign to appropriate team member

2. Fix Development

   • Create a patch or workaround
   • Test the fix thoroughly
   • Document the changes

3. Release

   • Deploy the fix
   • Update affected versions
   • Notify users if necessary

4. Disclosure

   • Credit the reporter (with permission)
   • Publish security advisory
   • Update documentation

• Reporter: Kept informed throughout the process
• Users: Notified of critical vulnerabilities
• Public: Security advisories published after fix

When contributing lab configurations:

• No real IP addresses from production networks
• No real passwords or credentials
• No sensitive network topology information
• Using documentation IP ranges (RFC 5737)
• Generic hostnames and descriptions
• No SNMP community strings
• No Telnet passwords (or use placeholders)
• Configurations are educational only

1. Design: Consider security in lab design
2. Implement: Use safe, example configurations
3. Review: Peer review for security issues
4. Document: Clear documentation of intended use

• Keep Packet Tracer updated
• Don't share your Cisco NetAcad credentials
• Report any Packet Tracer vulnerabilities to Cisco
• Use official Cisco resources only

• Cisco Networking Academy
• Packet Tracer Download
• Cisco Security Advisories
• GitHub Security Advisories
• OWASP Top 10

For security-related questions or concerns:

• GitHub Issues: Security Issues
• Maintainer: H0NEYP0T-466

Last Updated: June 2026

Version: 1.0