Sample POC Use Cases

This guide covers sample POC use сases.

CMDB

1. Discover CSP^* assets using API.

2. Create workflows to take action, e.g., send a Slack notification when an asset meets specific criteria such as a missing tag.   

3. Create list views to show publicly accessible resources, e.g., S3 Buckets.

4. Add a custom field on a CSP asset to store customer-specific attributes, e.g., Cost Center. 

5. Propagate a custom field (e.g., Department) from a CSP Account object to every other asset under that account.

6. Associate all CSP assets with resource groups based on asset name or tag values. 

7. Create a custom object (e.g., Cluster) and associate all assets with it based on name or tag values. 

8. Display details about assets that were terminated over a specific period, e.g., more than 24 hours ago.

9. Create dependency maps between assets.

10. Create tickets in external issue management systems (e.g., Jira) when an asset meets certain criteria, such as CSP usage reaching 90% of a limit.

11. Integrate CMDB with cloud monitoring services to show CPU, disk, and network activity for each asset.

12. Import OS-level data into CMDB, such as running services, users, and installed software.

13. Build a report showing CSP asset counts and trends.

14. Create a dashboard showing infrastructure deployment across CSP regions/locations.

15. Show tagging coverage across different CSP assets.

16. Tag CSP assets from the Cloudaware UI.

17. Create reports that break down assets by customer tags.

18. Build and schedule reports to identify assets with missing tags.

^*Cloud Service Provider, e.g., AWS, Azure, GCP, Heroku, etc.

Change Management

1. Create approval processes when a CSP asset meets specific criteria, e.g., a new user without MFA..

2. Show timelines of changes for CSP assets..

Cost Management

1. Show the cost of individual CSP assets.

2. Show the cost of applications and resource groups.

3. Create dashboards to explore costs by CSP attributes (standard and custom), e.g., product, service, application, and department tags.

4. Show expenditures not associated with any application.

5. Demonstrate the ability to optimize cost, e.g. using rightsizing and policies that detect idle or underutilized resources.

6. Show optimal reservations based on current instances.

7. Demonstrate the ability to forecast spending for 1, 3, and 6 months.

8. Create workflows to take an action, e.g., send an email alert when asset costs exceed thresholds, such as MTD spend reaching 75% of the previous month.

Security

1. Identify deviations from CSP security best practices, e.g., public AWS S3 Buckets or users without MFA.

2. Deploy vulnerability scanning agents, e.g., Nessus, and perform scans.

3. Display missing, pending, and installed patches on Linux and Windows hosts.

4. Deploy host-based intrusion detection agents.

5. Identify the most vulnerable hosts based on scans, patching status, exposed ports, and running software.

6. Create workflows to send notifications (email/SNS/Slack) when non-standard ports are open to the internet.

Compliance  Engine

1. Demonstrate the Templates Library and deploy compliance policies from built-in templates.

2. Use the Policy List to review all deployed policies.

3. Show how to interpret policy results.

4. Clone and edit policies in Policy Editor, or create new custom policies.

5. Create reports showing Compliance Engine policy violations.

6. Create workflows to send alerts (email/Jira/Slack) when a new violation is detected.

7. Deploy CIS Benchmarks.

8. Show how how to handle policy results (tabs 'Related Objects' and 'Statistic History').

9. Create dashboards to view compliance by attributes such as account, policy type, non-compliance lifetime, and historical trend.

10. Create workflows to send alerts (email/Jira/Slack) when a new non-compliant benchmark check is detected.

Monitoring

1. integrate with monitoring tools (New Relic, AppDynamics, Datadog, Zabbix, Pingdom, SolarWinds, Sensu, Nagios):

   1. Display monitored assets.

   2. Retrieve monitoring telemetry.

   3. Map incidents to assets.

   4. Show assets with the highest number of incidents. 

2. Group incidents into cases based on specific criteria, e.g., Zabbix Condition ID.

3. Create alerts (SNS/Slack/email) for newly created incidents meeting certain criteria, e.g., high severity.

Log Management

1. Automatically discover, store, and display different types of logs (cloud and host level).

2. Provide sample queries for searching logs.

3. Detect log anomalies.

4. Send alerts based on log conditions (optional).

Backup and Replication

1. Configure backup policies for AWS EC2, RDS, RDS clusters, S3 buckets, and Google disks.

2. Display backup health on dashboards and CIs.

3. Configure backup retention periods.

4. Explain how to replicate EC2 images using tags.

5. Create workflows to send alerts on failed backups.