Skip to content

Security: alipbudiman/Stunting-Bot-Detection

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.0.x

Reporting a Vulnerability

We take security seriously. If you discover any security-related issues, please follow these steps:

  1. Do Not create a public GitHub issue
  2. Send an email to [alifbudimanwahabbi@domain.com] with details about the vulnerability or contact via whatsapp in +62 82113791904
  3. Include the following information:
    • Type of issue
    • Full paths of source files related to the issue
    • Location of the affected source code
    • Any special configuration required to reproduce the issue
    • Step-by-step instructions to reproduce the issue
    • Proof-of-concept or exploit code (if possible)
    • Impact of the issue

Security Measures Implemented

  1. Authentication Security

    • WhatsApp OTP verification
    • Rate limiting on authentication attempts
    • Session management with secure tokens
  2. Data Protection

    • Encrypted database connections
    • Sensitive data encryption at rest
    • HTTPS/TLS for all communications
  3. Input Validation

    • Sanitization of all user inputs
    • Protection against SQL injection
    • XSS prevention
  4. API Security

    • Rate limiting on API endpoints
    • API authentication required
    • Input validation on all endpoints
  5. OTP Security

    • Limited validity period (10 minutes)
    • Maximum retry attempts (3)
    • Cooldown period after failed attempts

Response Timeline

  • Initial Response: Within 24 hours
  • Status Update: Within 72 hours
  • Security Fix: Depending on severity
    • Critical: 24-48 hours
    • High: 72 hours
    • Medium: 1 week
    • Low: Next release

Security Best Practices

  1. Keep all dependencies updated
  2. Use secure configurations in production
  3. Regular security audits
  4. Monitor system logs
  5. Follow secure coding guidelines

There aren't any published security advisories