Skip to content

Commit 4ae4c2a

Browse files
committed
Initial commit
1 parent 190c3ab commit 4ae4c2a

17 files changed

Lines changed: 7128 additions & 0 deletions

.github/CODE_OF_CONDUCT.md

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
<p align="center">
2+
<a href="https://community.specterops.io/" target="_blank">
3+
<img alt="Community of SpecterOps - Creators of BloodHound" src=".github/GitHub-COC-Header.png" width="100%" style="max-width: 100%;">
4+
</a>
5+
</p>
6+
7+
## :white_check_mark: In Summary
8+
* **Be driven by curiosity**: Be curious and passionate about everything, this curiosity sparks and is what drives the community.
9+
* **Be excellent to each other**: All community members and Specters are expected to interact with each other with respect, consideration and, where disagreements occur, to hear each other's perspectives with an open mind.
10+
* **Right place, right time**: To keep discussions organized and prevent overcrowding of a single channel/post/issue, community members are expected to find the appropriate place for their question or discussion.
11+
* **Keep it legit**: Drive excitement and curiosity through genuine, open discussion, not advertising or 'marketing'.
12+
13+
## :handshake: Our Pledge
14+
We pledge to make our community welcoming, safe, and equitable for all.
15+
16+
We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
17+
18+
Our goal is to process the industry's understanding of adversary tradecraft in all of its capabilities. Our goal is education, abuse is always condemned.
19+
20+
## :thumbsup: Encouraged Behaviors
21+
While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
22+
23+
With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
24+
25+
1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
26+
2. Engaging **kindly and honestly** with others.
27+
3. Respecting **different viewpoints** and experiences.
28+
4. **Taking responsibility** for our actions and contributions.
29+
5. Gracefully giving and accepting **constructive feedback**.
30+
6. Committing to **repairing harm** when it occurs.
31+
7. Behaving in other ways that promote and sustain the **well-being of our community**.
32+
33+
34+
## :no_entry_sign: Restricted Behaviors
35+
We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
36+
37+
1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
38+
2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
39+
3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
40+
4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
41+
5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
42+
6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
43+
7. Behaving in other ways that **threaten the well-being** of our community.
44+
8. **Non-constructive engagement.** Asking simple questions without research or with possible malicious intent. For example '_How to hack X_', '_Help me hack into..._'.
45+
9. **Abuse of tools and knowledge**. Abuse is strictly prohibited and will not be tolerated in the community. We share knowledge for educational purposes and to be used only in authorized environments only.
46+
47+
### Other Restrictions
48+
1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
49+
2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
50+
3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
51+
4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
52+
5. **Unauthorized usage of data.** (Personal) Information that is shared in the community will never be used without prior acknowledgement (and explicit opt-in) of the individual subject. This includes, but is not limited to newsletter sign-up or creation of accounts on third-party systems.
53+
54+
## :speaking_head: Reporting an Issue
55+
Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
56+
57+
When an incident does occur, it is important to report it promptly. To report a possible violation, contact the appropriate **channel's moderator** or contact us at **community[@]specterops.io**.
58+
59+
Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
60+
61+
62+
## :hammer: Addressing and Repairing Harm
63+
If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
64+
65+
1) Warning
66+
1) Event: A violation involving a single incident or series of incidents.
67+
2) Consequence: A private, written warning from the Community Moderators.
68+
3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
69+
2) Temporarily Limited Activities
70+
1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
71+
2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
72+
3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
73+
3) Temporary Suspension
74+
1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
75+
2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
76+
3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
77+
4) Permanent Ban
78+
1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
79+
2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
80+
3) Repair: There is no possible repair in cases of this severity.
81+
This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
82+
83+
## :straight_ruler: Scope
84+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
85+
86+
87+
## :blue_book: Attribution
88+
This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
89+
90+
Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
91+
92+
For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

.github/CONTRIBUTING.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
<p align="center">
2+
<a href="https://community.specterops.io/" target="_blank">
3+
<img alt="Community of SpecterOps - Creators of BloodHound" src=".github/GitHub-CONTRIB-Header.png" width="100%" style="max-width: 100%;">
4+
</a>
5+
</p>
6+
7+
## 💡 How to Contribute
8+
We welcome contributions from the community! Here's how you can help:
9+
1. **Issues**: Feel free to open issues for bugs, feature requests, or questions
10+
2. **Pull Requests**: Small improvements and bug fixes are welcome
11+
3. **Discussions**: Use GitHub Discussions for general questions and ideas
12+
13+
## ⚙️ Contribution Process
14+
1. Fork the repository
15+
2. Create a feature branch
16+
3. Make your changes with clear commit messages
17+
4. Submit a pull request with a description of changes
18+
5. The maintainer(s) will review and provide feedback
19+
20+
## 💬 Communication Channels
21+
- **Primary**: GitHub Issues and Pull Requests
22+
- **General Discussion**: GitHub Discussions
23+
- **Security Issues**: [GitHub Private Vulnerability Reporting](SECURITY.MD) for security issues or private matters
24+
- **Community Chat**: Slack message in the appropriate channel on [BloodHound Gang Slack](https://slack.specterops.io)
25+
26+
## 🕐 Response Times
27+
Given the nature of how SpecterOps manages open-source contributions, response may be delayed by the maintainer. If you have a pressing matter and do not receive a response, first reach out via the communication channels mentioned above.
28+
29+
If the maintainer still does not reply, please contact us at community[@]specterops.io.
30+
31+
## 🤝 Code of Conduct
32+
This project follows the [SpecterOps Community Code of Conduct](CODE_OF_CONDUCT.md). We expect all contributors to adhere to these guidelines to maintain a welcoming and inclusive community.
33+
34+
## ℹ️ Questions?
35+
If you have questions about contributing, feel free to open a GitHub Discussion or reach out through our [community channels](https://community.specterops.io).

.github/GOVERNANCE.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
<p align="center">
2+
<a href="https://community.specterops.io/" target="_blank">
3+
<img alt="Community of SpecterOps - Creators of BloodHound" src=".github/GitHub-GOV-Header.png" width="100%" style="max-width: 100%;">
4+
</a>
5+
</p>
6+
7+
## A Push to Transparency
8+
At SpecterOps, we believe that we can influence our industry's maturation by contributing to the collective knowledge base. We do this by opening our ideas and hypotheses to inspection and criticism. That includes publishing our development works and contributing to the open-source community.
9+
10+
SpecterOps employees control their own projects and maintain intellectual property rights and licenses, so not all projects supported by SpecterOps are consolidated under our [own repository](https://github.com/SpecterOps). We also maintain a separate list of open-source tooling on the [SpecterOps website](https://specterops.io/resources/?category%5B%5D=open_source_tools).
11+
12+
You can read more about our commitment to transparency in our blog post: [A Push Toward Transparency](https://specterops.io/blog/2018/05/04/a-push-toward-transparency/).
13+
14+
## Maintainers
15+
The primary maintainers are responsible for this repository. You can find them on the repository [contributors page](/graphs/contributors).
16+
17+
## Decision Making
18+
The project's maintainer(s) make all final decisions regarding:
19+
- Feature additions and removals
20+
- Architecture changes
21+
- Release schedules
22+
- Code quality standards
23+
24+
### Community Input
25+
Community input is always valued:
26+
- Breaking changes will have advance notice when possible
27+
- Feature requests are considered based on project goals
28+
- Open discussions on the [SpecterOps Community Channels](https://community.specterops.io)
29+
30+
## Project Goals
31+
All our projects share one common goal: To demystify adversary tradecraft through research and education.
32+
33+
## Project Status
34+
Unless archived, this is considered an actively maintained project.

.github/GitHub-COC-Header.png

485 KB
Loading

.github/GitHub-CONTRIB-Header.png

484 KB
Loading

.github/GitHub-GOV-Header.png

487 KB
Loading

.github/GitHub-Header.png

486 KB
Loading

.github/GitHub-LIC-Header.png

483 KB
Loading

.github/GitHub-SEC-Header.png

483 KB
Loading

.github/SECURITY.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
<p align="center">
2+
<a href="https://specterops.io/" target="_blank">
3+
<img alt="Community of SpecterOps - Creators of BloodHound" src=".github/GitHub-SEC-Header.png" width="100%" style="max-width: 100%;">
4+
</a>
5+
</p>
6+
7+
## :lock: Security Policy
8+
If you discover a security vulnerability in this project, we appreciate your help in disclosing it to us responsibly.
9+
10+
## :email: Reporting a Vulnerability
11+
Please do not report security vulnerabilities through public GitHub issues.
12+
Instead, please report security vulnerabilities using one of the following methods:
13+
14+
**1. GitHub Private Vulnerability Reporting**
15+
Send a private message to the repository maintainer(s) via GitHub. This keeps the vulnerability confidential while we work on a fix.
16+
17+
**2. Escalation: Community Slack**
18+
If you do not receive a timely response, or if the issue is time-sensitive, you can reach out to the maintainer(s) directly via the [BloodHound Gang Slack](https://slack.specterops.io).
19+
20+
**3. Last resort: Email**
21+
For sensitive matters or if the above channels are unavailable, you can email us at
22+
**community[@]specterops.io**.
23+
24+
## :pencil2: What to Include
25+
When reporting a vulnerability, please include:
26+
- Description of the vulnerability
27+
- Steps to reproduce the issue
28+
- Potential impact of the vulnerability
29+
- Any suggested fixes (if applicable)
30+
31+
## :beginner: Disclosure Policy
32+
- We request that you do not publicly disclose the vulnerability until we have had a chance to address it
33+
- Once a fix is available, we will coordinate with you on the timing of public disclosure
34+
- We will credit you for the discovery (unless you prefer to remain anonymous)
35+
36+
## :construction: Supported Versions
37+
Unless stated otherwise, only the latest version is supported. Refer to this project's documentation for more information about supported versions.

0 commit comments

Comments
 (0)