NetApp Ransomware Resilience Volume Snapshot Playbook
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
↑ Back to Content Index
This playbook creates a NetApp volume snapshot using the updated NetApp Ransomware Resilience take-snapshot API endpoint and optionally polls for completion.
Logic App Connectors
This playbook uses 1 Logic App connector / built-in action:
| Connector / Action |
Type |
Connections |
Actions |
http |
Built-in |
0 |
3 |
Action parameters (URLs, paths, function IDs)
http (Built-in)
| Action |
Method |
Endpoint |
Other |
| Call_Auth_Playbook |
POST |
[listCallbackUrl(resourceId('Microsoft.Logic/workflows/triggers', parameters('NetAppRansomwareResilienceAuthPlaybookName'), 'manual'), '2019-05-01').value] |
— |
| Submit_Volume_Snapshot |
POST |
https://api.bluexp.netapp.com/v1/services/rps/v1/account/@{variables('AccountId')}/storage/take-snapshot |
— |
| Call_Async_Poll_Playbook |
POST |
[listCallbackUrl(resourceId('Microsoft.Logic/workflows/triggers', parameters('NetAppRansomwareResilienceAsyncPollPlaybookName'), 'manual'), '2019-05-01').value] |
— |
Additional Documentation
📄 Source: NetApp-RansomwareResilience_Volume_Snapshot_Playbook/readme.md
NetApp-RansomwareResilience-Volume-Snapshot
Overview
This playbook creates point-in-time snapshots of NetApp volumes to protect your data. When responding to a security incident, snapshots provide a clean recovery point and preserve evidence for investigation.
Purpose
During a ransomware or security incident, taking immediate snapshots of critical volumes ensures you have a clean copy of data before any potential corruption or encryption occurs. These snapshots can be used for recovery or forensic analysis.
Deployment Order
This playbook should be deployed FIFTH, after:
- ✅ Auth Playbook (required)
- ✅ Async Poll Playbook (required)
- ✅ Enrich IP Playbook (optional)
- ✅ Enrich StorageVM Playbook (optional)
What It Does
- Accepts volume ID, agent ID, and system ID as input
- Retrieves authentication from the Auth Playbook
- Initiates a snapshot creation operation via the NetApp API
- Uses the Async Poll Playbook to monitor snapshot completion
- Confirms when the snapshot is successfully created
- Returns snapshot details and status
Prerequisites
Before deploying this playbook:
- Auth Playbook must be deployed and functioning correctly
- Async Poll Playbook must be deployed and functioning correctly
- Valid NetApp API credentials configured
- Sufficient storage capacity for snapshots
How to Use
This playbook can be:
- Called manually when you identify a volume that needs protection
- Triggered automatically by Microsoft Sentinel automation rules
- Integrated into multi-step incident response workflows
- Combined with enrichment playbooks to identify which volumes to snapshot
Input Required:
volume_id: The ID of the volume to snapshot
agent_id: The NetApp agent identifier
system_id: The NetApp system identifier
Use Case Example
Ransomware Incident Response:
- Receive alert about suspicious file encryption activity
- Use Enrich IP or Enrich StorageVM playbooks to identify affected volumes
- Use this playbook to immediately snapshot clean volumes
- Use Volume Offline playbook to isolate compromised volumes
- Restore from snapshots if needed
Important Notes
- Snapshots preserve the current state of the volume
- Snapshots consume storage space—monitor your capacity
- Take snapshots BEFORE taking volumes offline for maximum data protection
- Regular snapshots are recommended as part of your backup strategy
Post-Deployment Configuration
After deploying this playbook:
- Test with a non-production volume using valid IDs
- Verify the snapshot is created successfully
- Configure automation rules to trigger snapshots during security incidents
- Document your snapshot retention policies
Building Custom Workflows
Combine this playbook with others to create comprehensive incident response:
- Enrich IP → Identify volumes → Take snapshots → Take volumes offline
- Alert triggers → Enrich StorageVM → Take snapshots of all critical volumes
Need Help?
If snapshot creation isn't working, verify:
- The Auth Playbook is returning valid tokens
- The Async Poll Playbook is functioning correctly
- Volume ID, agent ID, and system ID are correct
- You have sufficient storage capacity for snapshots
- Your NetApp system supports snapshot operations
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
↑ Back to Playbooks · Back to NetApp Ransomware Resilience