Skip to content

Security: mtnvencenzo/azure-stack

.github/SECURITY.md

πŸ”’ Security Policy

πŸ›‘οΈ Supported Versions

We release patches for security vulnerabilities. Which versions are eligible for receiving such patches depends on the CVSS v3.0 Rating:

Version Supported
1.x.x βœ…
< 1.0 ❌

🚨 Reporting a Vulnerability

The Azure Stack team takes security bugs seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.

Where to Report

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them to the maintainer @mtnvencenzo

What to Include

To help us better understand the nature and scope of the possible issue, please include as much of the following information as possible:

  • 🎯 Type of issue (e.g., container escape, exposed credentials, insecure defaults, etc.)
  • πŸ“ Full paths of source file(s) related to the manifestation of the issue
  • πŸ“ Location of the affected source code (tag/branch/commit or direct URL)
  • βš™οΈ 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, including how an attacker might exploit the issue

πŸ“ž Response Timeline

  • Initial Response: Within 48 hours of receiving your report
  • Status Update: Within 7 days with a more detailed response
  • Resolution: We aim to resolve critical issues within 30 days

πŸ† Recognition

We believe in acknowledging security researchers who help improve our security:

  • πŸ“ Security Advisory: We will credit you in the security advisory (unless you prefer to remain anonymous)
  • πŸŽ–οΈ Hall of Fame: Recognition in our security contributors list

πŸ” Security Best Practices

For Users

  • πŸ”„ Keep Updated: Always use the latest version of the Docker images
  • πŸ”‘ Network Security: Run containers on isolated networks when possible
  • 🌐 Local Use Only: These emulators are designed for local development only
  • πŸ“± Environment Security: Keep your Docker environment and host system updated

For Developers

  • πŸ›‘οΈ Container Security: Use official Microsoft images for Azure service emulators
  • πŸ”’ Network Isolation: Configure proper network segmentation
  • πŸ“Š Monitoring: Monitor container logs for unusual activity
  • πŸ”„ Updates: Keep Docker images updated via Dependabot

πŸ“š Additional Resources

πŸ“‹ Security Checklist

Our security measures include:

  • βœ… Official Images: Using only official Microsoft Azure emulator images
  • βœ… Network Isolation: Containers run on isolated Docker networks
  • βœ… Local Development: Services designed for local development environments only
  • βœ… Dependency Scanning: Automated via Dependabot
  • βœ… Regular Updates: Keeping emulator images current
  • βœ… Documentation: Clear security guidelines and best practices

Thank you for helping keep Azure Stack and our users safe! πŸ”΅

There aren’t any published security advisories