NMAP-AI is a security tool designed for cybersecurity professionals, penetration testers, and network administrators. As such, we take security extremely seriously and are committed to maintaining the highest security standards.
| Version | Supported |
|---|---|
| 1.0.x | β Fully Supported |
| 0.9.x | |
| < 0.9 | β No Support |
We believe in responsible disclosure and appreciate the security community's help in keeping NMAP-AI secure. If you discover a security vulnerability, please follow these steps:
- Do not file public GitHub issues for security vulnerabilities
- Do not discuss the vulnerability in public forums
- Do not publish the vulnerability details publicly
- Email: security@nmap-ai.org
- PGP Key: Available at https://nmap-ai.org/security/pgp-key.asc
- Subject Line: "Security Vulnerability Report - NMAP-AI"
- Description: Clear description of the vulnerability
- Impact: Potential impact and risk assessment
- Reproduction Steps: Step-by-step reproduction instructions
- Environment: Operating system, Python version, NMAP-AI version
- Proof of Concept: Working proof of concept (if applicable)
- Suggested Fix: Proposed solution (if available)
- Acknowledgment: Within 24 hours
- Initial Assessment: Within 72 hours
- Regular Updates: Every 5 business days
- Resolution Target: Based on severity (see below)
- Response Time: Immediate (within 4 hours)
- Resolution Target: 24-48 hours
- Examples: Remote code execution, privilege escalation, data exposure
- Response Time: Within 8 hours
- Resolution Target: 5-7 days
- Examples: Authentication bypass, significant data leakage
- Response Time: Within 24 hours
- Resolution Target: 14-30 days
- Examples: Limited information disclosure, DoS conditions
- Response Time: Within 72 hours
- Resolution Target: 30-90 days
- Examples: Minor information disclosure, low-impact issues
We recognize security researchers who help improve NMAP-AI:
[Researchers who report valid vulnerabilities will be listed here with their permission]
- Valid Security Issue: Confirmed vulnerability affecting NMAP-AI
- Responsible Disclosure: Followed our disclosure process
- Constructive Report: Clear, actionable vulnerability report
- Permission: Researcher agrees to be listed
- Network Targets: Comprehensive validation of IP addresses and ranges
- Scan Parameters: Sanitization of all user inputs
- Script Injection: Protection against command injection attacks
- File Paths: Secure handling of file system operations
- Multi-factor Authentication: Support for 2FA/MFA
- Role-based Access: Granular permission controls
- Session Management: Secure session handling
- API Authentication: JWT and API key validation
- Encryption at Rest: AES-256 encryption for stored data
- Encryption in Transit: TLS 1.3 for all network communications
- Key Management: Secure key generation and storage
- Data Sanitization: Secure deletion of sensitive data
- Rate Limiting: Protection against scanning abuse
- IP Filtering: Whitelist/blacklist functionality
- Proxy Support: SOCKS and HTTP proxy integration
- Network Isolation: Containerization support
- Security Events: Comprehensive security event logging
- Audit Trails: Detailed audit logs for all actions
- Anomaly Detection: Detection of unusual patterns
- Real-time Monitoring: Active monitoring of security metrics
- Static Analysis: Automated code security scanning
- Dependency Scanning: Regular dependency vulnerability checks
- Code Reviews: Mandatory security-focused code reviews
- Secure Coding Standards: Following OWASP guidelines
- Security Testing: Automated security test suites
- Penetration Testing: Regular third-party security assessments
- Fuzzing: Automated fuzz testing of inputs
- Integration Testing: Security-focused integration tests
- Container Security: Docker image security scanning
- Infrastructure as Code: Secure infrastructure deployment
- Secrets Management: Secure handling of secrets and credentials
- Update Management: Regular security updates and patches
NMAP-AI should only be used on networks where you have:
- Explicit Permission: Written authorization from network owners
- Legal Authority: Proper legal authority to conduct scanning
- Professional Scope: Within the scope of authorized security assessments
- Unauthorized Scanning: Scanning networks without permission
- Malicious Activities: Using the tool for illegal purposes
- Privacy Violations: Unauthorized access to private information
- Harassment: Using the tool to harass or intimidate others
- Rate Limiting: Use appropriate scan timing to avoid disruption
- Scope Management: Stay within authorized testing scope
- Data Handling: Securely handle and dispose of scan results
- Disclosure: Follow responsible vulnerability disclosure practices
- Automatic Updates: Optional automatic security updates
- Security Notifications: Email alerts for critical security updates
- Change Logs: Detailed security-focused change logs
- Version Control: Clear versioning for security releases
- Critical Vulnerabilities: Immediate patch releases
- Out-of-band Updates: Emergency updates outside regular schedule
- Hotfixes: Rapid deployment of critical security fixes
- Communication: Clear communication about emergency updates
- Download from official sources only
- Verify cryptographic signatures
- Use latest stable version
- Review dependencies for known vulnerabilities
- Configure secure storage locations
- Use strong authentication credentials
- Enable audit logging
- Configure appropriate access controls
- Set up secure backup procedures
- Review and harden configuration settings
- Obtain proper authorization before scanning
- Use minimum necessary privileges
- Monitor for suspicious activities
- Keep software updated
- Follow incident response procedures
-
Immediate Actions
- Stop the potentially compromised activity
- Document the incident details
- Preserve evidence
- Contact our security team
-
Reporting
- Email: security@nmap-ai.org
- Include: Timeline, impact, affected systems
- Provide: Log files, screenshots, error messages
-
Response Support
- We provide incident response assistance
- Technical support for security incidents
- Coordination with your security team
- Post-incident analysis and recommendations
- Primary Contact: security@nmap-ai.org
- PGP Key: https://nmap-ai.org/security/pgp-key.asc
- Response Time: 24 hours for security issues
- Critical Issues: Use "URGENT SECURITY" in subject line
- After Hours: Critical issues receive immediate attention
- Escalation: Automatic escalation for high-severity issues
| Version | Date | Changes |
|---|---|---|
| 1.0 | July 2025 | Initial security policy |
This security policy is regularly reviewed and updated to reflect current best practices and emerging threats. Last updated: July 21, 2025
Remember: Security is everyone's responsibility. When using NMAP-AI, always follow ethical hacking principles and obtain proper authorization before conducting any network scanning activities.