Dillon Lees retweeted
Have Docker? Run BloodHound CE with one command:
curl -L github.com/SpecterOps/BloodH… | docker compose -f - up
Dillon Lees retweeted
We're thrilled to announce BloodHound Community Edition (CE) -- the next evolution of #BloodHound.
Scheduled for release on 8/8, BloodHound CE has many new features & enhancements, making it easier for users to deploy, manage, and utilize.
Learn more: ghst.ly/458lIGX
Dillon Lees retweeted
Want to see #BloodHoundEnterprise in action? Want to see what it actually, you know, DOES?
Register for and attend this webinar hosted by @Jonas_B_K, happening TOMORROW (Thursday, September 15): quest.com/event/practical-ap…
Webinar on Thursday📽️: Practical approach to secure critical assets in Active Directory and Azure
@bryanjpatton and I will discuss how to secure critical assets using the combination of BloodHound Enterprise and other great tools from @Quest. Event link in the first comment!
Dillon Lees retweeted
In the 2nd/final part of this series:
1⃣ How you can use BARK to accelerate your #Azure security research
2⃣ How the #BloodHoundEnterprise team uses BARK for continuous abuse primitive validation
3⃣ How BARK uses #PowerShell 7 features to go super fast
posts.specterops.io/automati…
Dillon Lees retweeted
We built #BloodHoundEnterprise to solve the problem of attack paths. In this customer testimonial, you can see how we are doing exactly that for one of our customers, @WoodsideEnergy:
bloodhoundenterprise.io/wp-c…
Dillon Lees retweeted
Red teamers: understand that in almost all instances, you do not need to execute your Azure abuses from a system your target manages. Azure is primarily API based. Those APIs are (nearly always) exposed to the internet.
Your customer isn't running EDR on YOUR machine.
Dillon Lees retweeted
The #BloodHoundEnterprise is proud to announce the release of #BloodHound 4.2: The Azure Refactor!
This is a HUGE release. Get all the details in this blog post: posts.specterops.io/1cff7349…
Dillon Lees retweeted
We are releasing #BloodHound 4.2 soon. In the meantime, check out the difference between the design of BloodHound 1.0's graph and BloodHound 4.2's graph:
