In SpartanX, an asset is any application, service, server, API, or code repository that forms part of your environment. Assets sit underneath collections and give you the level of detail where security analysis becomes practical and actionable.
An asset can represent many types of targets, depending on the collection it belongs to. This makes the asset model flexible enough to support cloud systems, applications, infrastructure, and code repositories in a single platform.
Examples of assets by collection
Collection | Example assets |
Cardholder Data Environment | Payment applications, transaction APIs, databases |
Perimeter | Firewalls, routers, reverse proxies, servers |
Code Repositories | GitHub repositories, GitLab instances |
Web Applications | External-facing applications and internal portals |
Use the Assets tab for focused management
The Assets tab lets you narrow your view and act quickly on the specific systems that matter.
Action | What it helps you do |
Filter by collection | View only the assets inside a selected collection |
Filter by asset | Narrow the list to one or more specific targets |
Launch an engagement directly | Start testing from the asset view without reopening the full wizard |
This makes the Assets tab useful for both day-to-day management and rapid follow-up testing.
Review the asset detail view
Opening an individual asset gives you a full profile of that target.
Area | What it shows |
Risk Overview | Current risk score, severity distribution, status, and asset type |
Business Impact | Manual override of impact level with required rationale and audit trail |
Vulnerabilities | Findings tied to the specific asset |
Ports | Open ports identified during testing |
Compliance Tags | Frameworks applied at collection or asset level |
Asset Ownership | Team and individual ownership for remediation |
The Business Impact field is especially useful because it allows teams to apply real business context where necessary. SpartanX provides an initial classification, but if an asset is less or more important than the platform's initial assessment, you can adjust it with a documented reason.
Apply compliance and ownership thoughtfully
Compliance can be assigned both broadly and precisely. A collection can carry a general framework mapping, while an individual asset can receive additional tags if it falls under a more specific obligation. Ownership can also be assigned at the asset level so the responsible team or person is clearly identified.
This helps turn asset management into a practical operational workflow instead of a passive inventory.
Export asset information
SpartanX lets you export either all assets in the current filtered view or only the specific assets you choose. This gives teams flexibility when preparing reviews, reporting packages, or internal handoffs.
Include code repositories as assets
Assets are not limited to infrastructure. Code repositories can also be brought into SpartanX through supported integrations, allowing the platform to assess repository-based targets alongside the rest of your environment.