Updating ransomware hashes in Cisco FTD to block ransomwares
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2024 06:41 AM
Hi All,
I would really appreciate your help regarding below issue.
I have received below hashes and we would like to update those hashes in FTD to block this qilin ransomware. Please let me know steps I should follow to update these hashes in the firewall.
Time/Date IOC occurred | IOC (SHA-256) | IOC Type | Context on why the IOC is suspicious/malicious |
NA | e90bdaaf5f9ca900133b699f18e4062562148169b29cb4eb37a0577388c22527 | File | qilin.exe |
NA | 73b1fffd35d3a72775e0ac4c836e70efefa0930551a2f813843bdfb32df4579a | File | 73b1fffd35d3a_edr72775e0ac4c836e70efefa0930551a2f813843bdfb32df4579aXxX17Exe.exe |
NA | 55e070a86b3ef2488d0e58f945f432aca494bfe65c9c4363d739649225efbbd1 | File | AgendaRansomware.exe |
NA | 37546b811e369547c8bd631fa4399730d3bdaff635e744d83632b74f44f56cf6 | File | 37546b811e369547c8bd631fa4399730d3bdaff635e744d83632b74f44f56cf6.exe |
NA | f837f1cd60e9941aa60f7be50a8f2aaaac380f560db8ee001408f35c1b7a97cb | File | f837f1cd60e9941aa60f7be50a8f2aaaac380f560db8ee001408f35c1b7a97cb.exe |
NA | 555964b2fed3cced4c75a383dd4b3cf02776dae224f4848dcc03510b1de4dbf4 | File | 555964b2fed3cced4c75a383dd4b3cf02776dae224f4848dcc03510b1de4dbf4.elf |
NA | 76f860a0e238231c2ac262901ce447e83d840e16fca52018293c6cf611a6807e | File | 1.exe |
NA | 117fc30c25b1f28cd923b530ab9f91a0a818925b0b89b8bc9a7f820a9e630464 | File | enc.exe |
NA | ae7c868713e1d02b4db60128c651eb1e3f6a33c02544cc4cb57c3aa6c6581b6e | File | ae7c868713e1d02b4db60128c651eb1e3f6a33c02544cc4cb57c3aa6c6581b6e.bin |
NA | cd27a31e618fe93df37603e5ece3352a91f27671ee73bdc8ce9ad793cad72a0f | File | cd27a31e618fe93df37603e5ece3352a91f27671ee73bdc8ce9ad793cad72a0f_unpacked |
NA | 28aeb2d6576b2437ecab535c0a1bf41713ee9864611965bf1d498a87cbdd2fab | File | pwndll.dll |
NA | fd7cbadcfca84b38380cf57898d0de2adcdfb9c3d64d17f886e8c5903e416039 | File | svchost.exe |
NA | e4a319f7afafbbd710ff2dbe8d0883ef332afcb0363efd4e919ed3c3faba0342 | File | e4a319f7afafbbd710ff2dbe8d0883ef332afcb0363efd4e919ed3c3faba0342.bin |
NA | 0629cd5e187174cb69f3489675f8c84cc0236f11f200be384ed6c1a9aa1ce7a1 | File | 0629cd5e187174cb69f3489675f8c84cc0236f11f200be384ed6c1a9aa1ce7a1.elf |
NA | 93d0cc8492511c663f17544b3bf14eab8ccb492909536e79ef652921d809bb1a | File | Associated with Agenda ransomware |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2024 08:17 AM
You can add the hashes to a file list as described here:
Note that we only see the file hashes at the firewall if they are transiting in an unencrypted (plain text) form or have been decrypted (i.e., via an SSL Decryption policy). So for 90%+ of Internet traffic (SSL/TLS-encrypted https) we never see the file hash at a perimeter firewall. Endpoint protection is the better place for this type of inspection and analysis.
