Skip to main content

Projects

Path: /applications (grouped by Project) · Sidebar: Assets

Projects are the top of the asset hierarchy - they group related Applications (e.g. all services in a product) so risk and posture roll up to a product owner.

The asset hierarchy​

Project  →  Application  →  Target  →  Scan  →  Finding
(product)   (app/service)  (URL/repo)  (run)    (issue)
  • Project - a product or business unit; the roll-up for leadership.
  • Application - a single app/service/repo; the risk-ownership unit.
  • Target - a scannable URL or connected repo.

Why use them​

  • Product posture - one score and grade per product, not per service.
  • Ownership - a project has an owner team; findings escalate to the right people.
  • Reporting scope - a stable axis for reports, scorecards and SLA.

For cross-cutting bundles that don't fit the tree (e.g. "all PCI-scope apps" across products), use tags or Target Groups instead.

Last updated on