Skip to content

Commit

Permalink
Update security policy URL.
Browse files Browse the repository at this point in the history
  • Loading branch information
ropable committed Jan 6, 2025
1 parent 8f7a5a8 commit a509473
Showing 1 changed file with 9 additions and 9 deletions.
18 changes: 9 additions & 9 deletions SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ source code repositories managed through our GitHub organisation

This repository takes guidance relating to Secure Software Development from the
[WA Government Cyber Security
Policy](https://www.wa.gov.au/system/files/2022-01/WA%20Government%20Cyber%20Security%20Policy.pdf).
Policy](https://www.wa.gov.au/government/publications/2024-wa-government-cyber-security-policy).

If you believe that you have found a security vulnerability in any DBCA-managed
repository, please report it to us as described below.
Expand All @@ -17,21 +17,21 @@ repository, please report it to us as described below.
**Please do not report security vulnerabilities through public GitHub issues.**

Instead, please report any security vulnerabilities to
[OIMSecurity@dbca.wa.gov.au](mailto:OIMSecurity@dbca.wa.gov.au).
[cyber@dbca.wa.gov.au](mailto:cyber@dbca.wa.gov.au).

You should receive a response within 1-2 business days. If for some reason you
do not, please follow up via email to ensure we received your original message.

Please include the requested information listed below (as much as you can provide)
to help us better understand the nature and scope of the possible issue:

* Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
* Full paths of source file(s) related to the manifestation of the issue
* The location of the affected source code (tag/branch/commit or direct URL)
* 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, including how an attacker might exploit the issue
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- 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, including how an attacker might exploit the issue

This information will help us triage your report more quickly. Please note that
we prefer all communications to be in English.
Expand Down

0 comments on commit a509473

Please sign in to comment.