Adding tools
Add the products in your security stack so Forest can map them to capabilities and surface coverage and overlap.
Last updated June 1, 2026
Before the Forest Map can show you anything useful, it needs to know what is in your stack. Adding tools is how you tell Forest which products you own and use.
A tool in Forest is a specific product, drawn from the vendor and product catalog. When you add one, you select it from the catalog so that it carries a consistent identity and a known set of capability mappings. This is what lets Forest compare your stack to peers and reason about overlap with confidence.
Work through your stack in the order that reflects spend and importance:
Add the platforms that anchor each domain, such as your identity provider or endpoint protection.
Add point tools that cover narrower capabilities.
Add anything that overlaps with what you already entered, since overlap is often where money leaks.
For each tool, you confirm how it maps to capabilities. Some mappings come pre-populated from the catalog. Others you confirm or adjust based on how you actually deploy the product. The difference matters, and it is covered in Confirmed vs inferred mappings.
Add tools you actually run, not tools you have licensed but never deployed. A shelved license inflates your apparent coverage and hides a real gap.
If a product is not in the catalog, see Vendor and product catalog rules for how naming and entries are handled. Once your tools are in, the Map can begin surfacing overlap and gaps.