Asset management in FigoRisk helps you maintain a comprehensive inventory of all organizational assets, assess their value and criticality, and understand associated risks.
Why asset management matters: You can’t protect what you don’t know
exists. A complete asset inventory is the foundation of effective risk
management.
Asset Details: - Asset Name: Descriptive name (e.g., “Production Web
Server”) - Asset Type: Select from Hardware, Software, Data, Network -
Category: More specific classification - Description: Brief
description of the asset Example:Name: Customer Database Server Type: Hardware Category: Database Server Description: Primary MySQL server hosting customer data
4
Set Asset Criticality
Criticality Level (Business impact if asset fails): - Critical:
Mission-critical, no alternative - High: Very important, minimal
alternatives - Medium: Important, alternatives available - Low: Nice
to have, easily replaceable
Ask: “What happens if this asset is unavailable for 24 hours?”
5
Add Technical Details
Hardware Assets: - Serial Number - IP Address - MAC Address - Location
(physical or data center) - Manufacturer - Model - Purchase Date - Warranty
Expiry Software Assets: - Version - License Type - License Expiry -
Vendor - Installation Date Data Assets: - Data Classification (Public,
Internal, Confidential, Restricted) - Data Type (PII, Financial, Health,
etc.) - Storage Location - Retention Period
6
Assign Ownership
Asset Owner: Primary responsible person - Department: Owning
department - Custodian: Person managing the asset - Users: People
who use this asset
7
Set Financial Information
Purchase Value: Original cost - Current Value: Depreciated value -
Annual Cost: Maintenance/license costs
Go to Assets page 2. Click Import Assets 3. Download CSV template
2
Prepare Your Data
Fill in the template with asset information: | Asset Name | Type | Category
| Criticality | Owner | IP Address | Location |
|-----------|------|----------|-------------|-------|-----------|----------|
| Web Server 01 | Hardware | Server | Critical | John Doe | 192.168.1.10 |
Data Center A | | CRM Application | Software | Business App | High | Jane
Smith | - | Cloud | | Customer Database | Data | Database | Critical | Bob
Johnson | - | AWS RDS |
3
Upload File
Click Choose File 2. Select your CSV 3. Click Upload
4
Review Preview
Check the import preview: - ✅ Valid entries (will be imported) - ⚠️
Warnings (will import but check data) - ❌ Errors (won’t import, fix
required)
5
Complete Import
Click Import Assets You’ll see a summary: - X assets imported
successfully - Y assets with warnings - Z assets failed (download error
report)
Before bulk import: Test with 5-10 assets first to ensure your CSV format
is correct.
Determine asset criticality based on business impact:
Critical
High
Medium
Low
Characteristics: - No alternatives or backups available - Immediate
business impact if unavailable - Affects revenue or regulatory compliance -
Downtime measured in minutes Examples: - Production payment gateway -
Primary customer database - Core banking system - Emergency communication
system
Characteristics: - Limited alternatives available - Significant business
impact - Affects operations or customer service - Downtime measured in hours
Examples: - Email server - CRM application - Internal ERP system - File
sharing platform
Characteristics: - Alternatives exist - Moderate business impact -
Affects productivity - Downtime measured in days Examples: - Project
management tools - Internal wiki - Development servers - HR management
system
Characteristics: - Easily replaceable - Minimal business impact - Nice
to have - Extended downtime acceptable Examples: - Test/demo
environments - Personal productivity tools - Archive servers - Training
systems
Click + Add DependencyTypes of relationships: - Depends On:
This asset requires another asset - Used By: This asset is used by
another asset - Hosted On: Software/data hosted on hardware - Connects
To: Network connections
4
Select Related Asset
Search and select the related asset
5
Save Relationship
Click Save
Example dependencies:
Copy
Web Application (Software)├── Depends On → Web Server (Hardware)├── Depends On → Database Server (Hardware)└── Contains → Customer Data (Data)Database Server (Hardware)├── Hosted On → VMware Cluster (Hardware)├── Connects To → SAN Storage (Hardware)└── Used By → Backup System (Software)
Complete list of all assets with key details Includes: - Asset name and
type - Owner and location - Criticality level - Status - Last updated date
Export as: PDF, Excel, CSV
Focus on mission-critical assets Includes: - All critical and high
priority assets - Associated risks - Compliance requirements - Recent
changes Use for: Management reviews, audit preparation
Assets grouped by responsible person Includes: - Owner name and contact
Assets assigned - Total asset value - Pending actions Use for:
Accountability reviews, resource planning
Assets by lifecycle status Includes: - Status distribution - Assets
pending retirement - Maintenance schedules - Acquisition pipeline Use
for: Capacity planning, budget forecasting
Maintenance Type: Routine, Repair, Upgrade - Scheduled Date: When
maintenance will occur - Duration: Expected downtime - Assigned To:
Technician responsible - Description: What will be done - Impact:
Expected business impact
Steps: 1. Create asset record before deployment 2. Set status to
“Planning” 3. Document specifications and requirements 4. Update to
“Acquisition” when ordered 5. Change to “Active” when deployed 6. Link to
dependent applications 7. Schedule first maintenance
Hardware Refresh
Steps: 1. Identify assets for replacement 2. Plan new asset acquisition
3. Create records for new assets 4. Schedule migration 5. Update status of
old assets to “Retired” 6. Transfer dependencies to new assets 7. Document
disposal process
Cloud Migration
Steps: 1. Document current on-premise assets 2. Create cloud asset
records 3. Map dependencies and relationships 4. Update locations during
migration 5. Retire on-premise assets when complete 6. Update cost
information 7. Verify all dependencies transferred
Asset Security Incident
Response: 1. Flag affected asset 2. Document incident details 3. Assess
impact using dependencies 4. Notify asset owner and users 5. Coordinate
remediation 6. Update asset status if needed 7. Record in asset history