Asset Types¶

Understanding the different types of assets discovered and managed in Hive.

Overview¶

Hive discovers and tracks multiple asset types, each representing different components of your attack surface.

Asset Type Hierarchy¶

graph TD
    A[Assets] --> B[URLs]
    A --> C[Sites]
    A --> D[Hosts]
    A --> E[IPs]
    A --> F[Ports]
    A --> G[DNS]
    A --> H[Applications]
    A --> I[Metadata]

    B --> B1[Endpoints]
    C --> C1[Web Properties]
    D --> D1[Servers]
    E --> E1[Network Addresses]
    F --> F1[Services]
    G --> G1[Domain Records]
    H --> H1[Software]
    I --> I1[Headers/Banners]

URL Assets¶

Definition: Specific web endpoints and pages

Examples: - https://example.com/login - https://api.example.com/v1/users - https://example.com/admin/dashboard

Attributes: - Full URL path - HTTP method - Status code - Response size - Content type - Parameters

Relationships: - Belongs to Site - Hosted on Host - May have Vulnerabilities

Use Cases: - Web application mapping - API endpoint discovery - Content enumeration - Attack surface mapping

📸 Screenshot: URL asset details

Site Assets¶

Definition: Web properties (domains/subdomains)

Examples: - example.com - www.example.com - api.example.com - admin.example.com

Attributes: - Domain name - Protocol (HTTP/HTTPS) - Web server - Technologies detected - SSL certificate info - HTTP headers

Relationships: - Contains URLs - Resolves to IP - Has DNS records - Runs Applications

Use Cases: - Subdomain tracking - Technology stack identification - SSL/TLS monitoring - Web server inventory

Host Assets¶

Definition: Physical or virtual servers

Examples: - web-server-01.example.com - db-primary.internal - mail.example.com

Attributes: - Hostname - Operating system - Open ports - Running services - Last seen - Response time

Relationships: - Has IP addresses - Hosts Sites - Runs Services - Has Ports open

Use Cases: - Server inventory - OS fingerprinting - Service mapping - Network topology

IP Address Assets¶

Definition: Network addresses (IPv4/IPv6)

Examples: - 203.0.113.42 (IPv4) - 2001:db8::1 (IPv6)

Attributes: - IP address - IP version (v4/v6) - Geolocation - ASN - Organization - Reverse DNS

Relationships: - Belongs to Host - Has open Ports - Associated with DNS - Network range

Use Cases: - Network mapping - IP range tracking - Geolocation analysis - ASN identification

Port Assets¶

Definition: Network service endpoints

Examples: - 203.0.113.42:443 (HTTPS) - 203.0.113.42:22 (SSH) - 203.0.113.42:3306 (MySQL)

Attributes: - Port number - Protocol (TCP/UDP) - Service name - Service version - Banner - State (open/closed/filtered)

Relationships: - Belongs to IP - Runs Service - May have Vulnerabilities - Has Metadata

Use Cases: - Service discovery - Version tracking - Vulnerability mapping - Access point inventory

📸 Screenshot: Port asset with service details

DNS Assets¶

Definition: Domain Name System records

Examples: - A record: example.com → 203.0.113.42 - CNAME record: www.example.com → example.com - MX record: mail.example.com - TXT record: SPF, DKIM records

Attributes: - Record type (A, AAAA, CNAME, MX, TXT, NS, etc.) - Domain name - Value/Target - TTL - Last updated

Relationships: - Points to IP - Associated with Site - Part of Domain

Use Cases: - Subdomain enumeration - DNS configuration tracking - Email security (SPF/DKIM) - Infrastructure mapping

Application Assets¶

Definition: Detected software and technologies

Examples: - WordPress 6.2.2 - nginx 1.21.6 - PHP 8.1.0 - jQuery 3.6.0

Attributes: - Application name - Version - Category (CMS, Web Server, Framework, etc.) - Confidence level - Detection method

Relationships: - Runs on Host - Used by Site - May have known Vulnerabilities - Part of Technology Stack

Use Cases: - Technology inventory - Version tracking - Vulnerability correlation - Patch management

Metadata Assets¶

Definition: Additional information from services

Examples: - HTTP headers - Server banners - SSL certificate details - Service configurations

Attributes: - Type (header, banner, certificate, etc.) - Key - Value - Source - Timestamp

Relationships: - Associated with Port - Belongs to Site - Provides context

Use Cases: - Configuration analysis - Security header checking - Banner grabbing - Certificate monitoring

Asset Attributes¶

Common Attributes¶

All Assets Have: - Unique ID - Discovery date - Last seen - Source (which scan found it) - Engagement - Tags - Notes

Custom Attributes¶

User-Defined: - Custom tags - Business criticality - Owner/Team - Environment (prod/staging/dev) - Compliance requirements

Asset Relationships¶

Relationship Types¶

Parent-Child: - Site contains URLs - Host has IPs - IP has Ports

Association: - URL uses Application - Port runs Service - Site has DNS records

Vulnerability: - Asset has Vulnerability - Vulnerability affects multiple Assets

Relationship Graph¶

Graph Visualization: 1. Navigate to Assets → Graph View 2. Select starting asset 3. Explore relationships 4. Filter by relationship type 5. Export graph

📸 Screenshot: Asset relationship graph

Asset Discovery¶

Discovery Methods¶

Automated Scanning: - Port scanning (Nmap, Masscan) - Web crawling (Burp, ZAP) - Subdomain enumeration (Amass, Subfinder) - Service detection - Technology fingerprinting

Manual Entry: - Import from CSV - API creation - Manual addition - Bulk import

Integration: - Cloud provider APIs - Configuration management - Asset management systems - Network monitoring

Asset Management¶

Viewing Assets¶

List View: 1. Navigate to Assets → All 2. Filter by type 3. Sort by column 4. Search 5. Select assets

Graph View: 1. Navigate to Assets → Graph View 2. Explore relationships 3. Filter connections 4. Zoom and pan

Table View: 1. Customizable columns 2. Export to CSV 3. Bulk actions 4. Advanced filters

Filtering Assets¶

Filter Options: - Type: URL, Site, Host, IP, Port, DNS, Application - Engagement: Specific engagement - Tags: Custom tags - Date: Discovery date range - Status: Active, Inactive - Severity: If has vulnerabilities

Saved Filters: 1. Apply filters 2. Click Save Filter 3. Name filter 4. Reuse anytime

Tagging Assets¶

Tag Uses: - Categorization - Ownership - Environment - Criticality - Compliance

Tag Management: 1. Select assets 2. Click Add Tag 3. Create or select tag 4. Apply to assets

Tag Examples: - production - critical - pci-scope - team-security - external-facing

Asset Actions¶

Bulk Actions: - Add tags - Remove tags - Assign to engagement - Export - Delete

Individual Actions: - View details - Edit attributes - Add notes - View vulnerabilities - View relationships

Asset Lifecycle¶

States¶

graph LR
    A[Discovered] --> B[Active]
    B --> C[Inactive]
    C --> D[Archived]
    B --> D

Discovered: Newly found asset
Active: Currently in use
Inactive: No longer responding
Archived: Removed from scope

Lifecycle Management¶

Automatic State Changes: - Asset discovered → Active - Asset not seen in 30 days → Inactive - Manual archive → Archived

Manual State Changes: 1. Select asset 2. Click Change State 3. Select new state 4. Add reason 5. Confirm

Asset Enrichment¶

Automatic Enrichment¶

During Discovery: - Geolocation lookup - ASN identification - Technology detection - Service fingerprinting - SSL certificate parsing

Continuous Enrichment: - Vulnerability correlation - Threat intelligence - Reputation checks - Compliance mapping

Manual Enrichment¶

Add Context: - Business owner - Criticality rating - Compliance requirements - Change history - Maintenance windows

Asset Reporting¶

Asset Reports¶

Generate Reports: 1. Navigate to Intelligence → Reporting Engine 2. Select Asset Report 3. Choose asset types 4. Configure options 5. Generate

Report Types: - Asset Inventory - Asset Changes - Technology Stack - Vulnerability by Asset - Compliance Report

Export Options¶

Export Formats: - CSV: Spreadsheet format - JSON: API format - PDF: Document format - XML: Structured data

Export Fields: - All attributes - Custom selection - Include relationships - Include vulnerabilities

Best Practices¶

Asset Management¶

✅ Regular Scanning: Keep inventory current
✅ Tag Consistently: Use standard tags
✅ Review Regularly: Check for changes
✅ Enrich Data: Add business context
✅ Archive Old Assets: Keep inventory clean
✅ Document Ownership: Know who owns what

Asset Security¶

✅ Monitor Changes: Track new assets
✅ Assess Criticality: Prioritize protection
✅ Scan Regularly: Find vulnerabilities
✅ Patch Quickly: Remediate issues
✅ Limit Exposure: Reduce attack surface

Troubleshooting¶

Assets Not Appearing¶

Check: - Scan completed successfully - Correct engagement selected - Filters not too restrictive - Asset in scope

Duplicate Assets¶

Causes: - Multiple discovery methods - DNS aliases - Load balancers

Solution: - Merge duplicates - Configure deduplication - Review discovery rules

Missing Relationships¶

Causes: - Incomplete scan - Network restrictions - Configuration issues

Solution: - Run comprehensive scan - Check network access - Review scan logs

Related: Asset Inventory | Graph View | Vulnerabilities