|
| 1 | +# Security Policy |
| 2 | + |
| 3 | +SharpADIDNS is a dual-use security and administration tool for AD-integrated |
| 4 | +DNS. This policy covers vulnerabilities in this project itself. It does not |
| 5 | +provide authorization to test, attack, or modify systems that you do not own or |
| 6 | +do not have explicit permission to assess. |
| 7 | + |
| 8 | +## Supported Versions |
| 9 | + |
| 10 | +This project does not maintain long-term support branches. Security fixes are |
| 11 | +handled for the latest tagged release and the `main` branch. |
| 12 | + |
| 13 | +| Version | Security support | |
| 14 | +| ------- | ---------------- | |
| 15 | +| Latest tagged release | Supported | |
| 16 | +| `main` branch | Supported on a best-effort basis | |
| 17 | +| Older tags or forks | Not supported | |
| 18 | + |
| 19 | +## Scope |
| 20 | + |
| 21 | +In scope: |
| 22 | + |
| 23 | +- Vulnerabilities in the SharpADIDNS source code. |
| 24 | +- Vulnerabilities in official release artifacts published from this repository. |
| 25 | +- Build, packaging, or documentation issues that could materially mislead users |
| 26 | + into unsafe operation. |
| 27 | +- Supply-chain or repository-integrity concerns affecting this project. |
| 28 | + |
| 29 | +Out of scope: |
| 30 | + |
| 31 | +- Abuse of expected SharpADIDNS functionality against systems without |
| 32 | + authorization. |
| 33 | +- Vulnerabilities in third-party environments, AD deployments, DNS |
| 34 | + configurations, C2 frameworks, or operator infrastructure. |
| 35 | +- Requests for help bypassing detection, access controls, or organizational |
| 36 | + policy in environments where you are not authorized. |
| 37 | +- Social engineering, physical attacks, spam, denial-of-service testing, or |
| 38 | + attacks against GitHub, maintainers, or project users. |
| 39 | +- Theoretical reports without a plausible impact path. |
| 40 | + |
| 41 | +## Reporting a Vulnerability |
| 42 | + |
| 43 | +Please do not disclose vulnerability details in a public issue, pull request, |
| 44 | +discussion, gist, social post, or chat transcript. |
| 45 | + |
| 46 | +Preferred reporting channel: |
| 47 | + |
| 48 | +- Use GitHub Private Vulnerability Reporting for this repository, if available: |
| 49 | + <https://github.com/RedteamNotes/SharpADIDNS/security/advisories/new> |
| 50 | + |
| 51 | +Fallback reporting channel: |
| 52 | + |
| 53 | +- If private reporting is not available, open a public issue titled |
| 54 | + `Security contact request` and include only a brief, non-sensitive summary. |
| 55 | + A maintainer can then arrange a private channel. |
| 56 | + |
| 57 | +Please include: |
| 58 | + |
| 59 | +- Affected version, tag, commit, or release artifact. |
| 60 | +- A clear impact statement and the security boundary being crossed. |
| 61 | +- Minimal reproduction steps or proof-of-concept details. |
| 62 | +- Relevant logs, command output, or screenshots with secrets removed. |
| 63 | +- Whether the issue is already publicly known or under active exploitation. |
| 64 | +- Any suggested remediation, if you have one. |
| 65 | + |
| 66 | +Do not include production credentials, tokens, private keys, customer data, |
| 67 | +domain names, IP addresses, or other sensitive environmental details unless the |
| 68 | +maintainer explicitly asks for them and a private channel has been agreed. |
| 69 | + |
| 70 | +## Handling and Disclosure |
| 71 | + |
| 72 | +Expected response targets: |
| 73 | + |
| 74 | +- Acknowledgement: within 3 business days. |
| 75 | +- Initial triage: within 7 business days. |
| 76 | +- Fix plan: based on severity, exploitability, affected versions, and release |
| 77 | + complexity. |
| 78 | + |
| 79 | +Target remediation windows after confirmation: |
| 80 | + |
| 81 | +| Severity | Target | |
| 82 | +| -------- | ------ | |
| 83 | +| Critical | 14 days | |
| 84 | +| High | 30 days | |
| 85 | +| Medium | Next reasonable release | |
| 86 | +| Low | Best effort | |
| 87 | + |
| 88 | +For issues with broad user impact, the project may publish a GitHub Security |
| 89 | +Advisory, request a CVE, or release coordinated mitigation guidance. Public |
| 90 | +credit will be offered unless the reporter requests otherwise. |
| 91 | + |
| 92 | +Please coordinate public disclosure with the maintainers. As a default, wait |
| 93 | +until a fix or mitigation is available, or 90 days after the issue is confirmed, |
| 94 | +whichever comes first, unless both sides agree to a different timeline. |
| 95 | + |
| 96 | +## Safe Harbor |
| 97 | + |
| 98 | +The project will not pursue legal action against good-faith security research |
| 99 | +that: |
| 100 | + |
| 101 | +- Targets only systems, accounts, repositories, and data you are authorized to |
| 102 | + test. |
| 103 | +- Avoids privacy violations, data destruction, persistence, lateral movement, |
| 104 | + and service disruption. |
| 105 | +- Uses the minimum testing necessary to demonstrate the issue. |
| 106 | +- Reports the issue promptly and keeps details confidential during coordinated |
| 107 | + disclosure. |
| 108 | +- Does not use the vulnerability for extortion, unauthorized access, or |
| 109 | + operational advantage. |
| 110 | + |
| 111 | +This safe harbor applies only to this project and its maintainers. It cannot |
| 112 | +bind third parties, employers, service providers, customers, or other legal |
| 113 | +owners of affected systems. |
| 114 | + |
| 115 | +## Secure Use Expectations |
| 116 | + |
| 117 | +SharpADIDNS is intended for authorized security assessments, lab environments, |
| 118 | +CTFs, and controlled administration work. Operators should prefer `--dry-run` |
| 119 | +and `--backup-to` before write operations, keep engagement authorization and |
| 120 | +change records, and avoid including secrets or customer-specific details in bug |
| 121 | +reports. |
| 122 | + |
| 123 | +The maintainers may decline reports or requests whose primary purpose is to |
| 124 | +enable unauthorized operation, evade policy in third-party environments, or |
| 125 | +provide offensive tasking support rather than improve the security of the |
| 126 | +project. |
0 commit comments