{"playbook_version":2,"artifacts":[{"id":"artifact_1","type":"ip","value":"203.0.113.45","is_critical":true,"osint_result":{"source":"Threat Intelligence Database","verdict":"malicious","details":"Known C2 server for Ryuk ransomware"}},{"id":"artifact_2","type":"ip","value":"192.168.1.25","is_critical":false,"osint_result":{"source":"Internal Network","verdict":"internal","details":"Internal host identified as victim"}},{"id":"artifact_3","type":"username","value":"jdoe","is_critical":false,"osint_result":{"source":"Internal User Directory","verdict":"internal","details":"Account used during the attack"}},{"id":"artifact_4","type":"filename","value":"READ_ME.txt","is_critical":true,"osint_result":{"source":"File Analysis","verdict":"malicious","details":"Standard ransom note file for Ryuk"}},{"id":"artifact_5","type":"hash","value":"3fa85f64-5717-4562-b3fc-2c963f66afa6","is_critical":true,"osint_result":{"source":"Malware Database","verdict":"malicious","details":"Hash associated with Ryuk ransomware"}}],"recommended_actions":["isolate_host","block_ip","block_hash","reset_credentials","collect_forensics","escalate"],"expected_verdict":"True Positive","expected_actions":["isolate_host","block_ip","block_hash","collect_forensics","escalate"]}