Skip to content

Security: canstralian/tafe-assignments

SECURITY.md

Dotcomhunters Security Policy

Reporting Security Vulnerabilities

If you believe you've found a security vulnerability in Dotcomhunters' repository, please send an email to [email protected]. We appreciate your help in responsibly disclosing the issue. We will work to address and resolve any reported vulnerabilities as quickly as possible.

Please do not publicly disclose the vulnerability until we've had a chance to address it.


For more information on our security practices and how we handle vulnerabilities, please refer to our Security Policy.

This policy is effective as of 13/08/2023.

Security Measures

Access Control

We implement strict access control measures to ensure that only authorized personnel have access to the repository. This includes:

  • Enforcing two-factor authentication (2FA) for all contributors.
  • Limiting administrative access to essential team members.
  • Regularly reviewing and revoking access for inactive contributors.

Code Reviews

All code changes are subject to thorough code reviews by team members. This process helps identify and address security vulnerabilities before they are merged into the main codebase.

Branch Protection

We enforce branch protection rules to control code changes and ensure secure coding practices. These rules include:

  • Requiring code reviews before merging.
  • Preventing force pushes to protected branches.
  • Requiring status checks to pass before merging.

Security Updates

We stay proactive in addressing security vulnerabilities by regularly updating dependencies, libraries, and frameworks. This ensures that our project is protected against known security vulnerabilities.

Reporting Suspicious Activity

If you notice any suspicious activity related to our repository, such as unauthorized access or changes, please report it to our security team immediately.

Acknowledgments

We want to thank all security researchers and contributors who help improve the security of our project. Your efforts are greatly appreciated.

For more information on our security practices and guidelines, please refer to our Security Policy.


Note: This document is a guideline and template for creating a SECURITY.md file. Actual details, contact information, and security practices may vary based on your organization's needs and policies.

There aren’t any published security advisories