# How do you prioritize fixes when NodeZero shows connected weaknesses and potential access paths?

I like that NodeZero from Horizon3 goes beyond a basic vulnerability list by showing how weaknesses connect and what someone could access after getting into the network. The proof behind the findings helps explain why certain fixes should be prioritized, and retesting fixes is useful to confirm changes actually worked. On the downside, some findings still take technical knowledge to understand and investigate, and planning tests carefully matters in production. How are others handling prioritization and retesting while keeping tests safe for production?

##### Post Metadata
- Posted at: 9 days ago
- Author title: Cybersecurity Analyst | Penetration Testing | Vulnerability Management | Security Operations
- Net upvotes: 1



## Related Product
[NodeZero from Horizon3](https://www.g2.com/products/nodezero-from-horizon3/reviews)

## Related Category
[Penetration Testing](https://www.g2.com/categories/penetration-testing-tools)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


