This weblog is continuation of the earlier weblog on utilizing Cisco Safe Community Analytics. On this half, we cowl leveraging public Cisco Talos blogs and third-party menace intelligence information with Cisco Safe Community Analytics. Remember to learn the primary half as this half makes references again to Host Group and Customized Safety Occasion directions coated within the unique weblog.
Cisco Talos Blogs
The proficient researchers at Cisco Talos frequently publish blogs on threats and vulnerabilities. These blogs break down the techniques, strategies and procedures (TTPs) utilized by menace actors. Talos’ analysis publications usually embody pattern supply code, phishing emails, reverse engineering of malicious binaries, instruments, scripts, command and management methodology, attacker infrastructure, file hashes, domains and IP addresses utilized in malicious operations. The symptoms of compromise (IOCs) are revealed on GitHub as JSON and plain textual content information. We will use these blogs and GitHub information to construct Customized Safety Occasions in Cisco Safe Community Analytics.
Let’s have a look at a weblog: MoonPeak malware from North Korean actors unveils new particulars on attacker infrastructure. This weblog focuses on a state-sponsored group from North Korea. The group leverages an open-source distant entry trojan (RAT) from a household being known as MoonPeak.
Scroll by the article and take note of the extent of element offered. Close to the very backside of the weblog discover the part titled IOCs.
Click on on the hyperlink to the GitHub repository. You can be taken to the Cisco Talos GitHub repository the place you can find the IOCs can be found as JSON and plain textual content information, and are sorted by the month the weblog was revealed in. Be happy to discover different information, months, and years to get aware of the symptoms frequently offered.
Click on on the file “moonpeak-infrastructure-north-korea.txt” or observe the direct hyperlink. Scroll right down to line 35 of the file the place the Community IOCs start. This record accommodates twelve IP addresses we’re keen on. Seen that the IP addresses and domains have been defanged with sq. brackets across the dots so you can not by accident click on on them.
You possibly can both manually delete the sq. brackets or use the discover and change performance in your favourite textual content editor to do the job. I want to make use of Notepad++ when coping with textual content information. I set the “Discover and Exchange” to search for the sq. brackets across the dot and change all situations with a dot.
Delete the domains from the record and replica and paste these IP addresses right into a New Host Group utilizing the strategies described within the first a part of this weblog.
You might also think about using a device to extract IP addresses from textual content. I actually like iplocation IP Extractor. You possibly can paste in a block of textual content with IPv4 and IPv6 IP addresses and it’ll extract them to allow them to be simply reviewed and pasted into a number group. The IPs you paste into this device can’t be defanged. It requires full and proper IP addresses to work.
At all times think about the sensitivity of the knowledge you present to public instruments earlier than utilizing them. It is best to think about a domestically hosted device for delicate data
Third-party menace intelligence
If you happen to take part in any Info Sharing and Evaluation Facilities (ISACs), subscribe to industrial feeds or frequently make the most of bulletins and blogs geared in direction of your business, you may as well make the most of their indicators in Cisco Safe Community Analytics. They work the identical method we dealt with inside menace intelligence within the first a part of this weblog or Cisco Talos blogs proven above. Watch out when scraping menace intelligence to make certain you’re solely together with indicators you propose to make use of. For instance, in case you are scraping a whole bulletin that accommodates IP addresses you have an interest in, ensure you don’t by accident copy an IP tackle from an adjoining and unrelated entry.
You possibly can paste a block of IP addresses right into a New Host Group or use a device to tug them out of a block of textual content after which paste them. Watch out in case your supply defangs IP addresses, as this is quite common. You should use the identical strategies I illustrated for the Cisco Talos GitHub entries above.
Host group dad or mum/baby relationships
apply for constructing dad or mum and baby host teams is to create a brand new dad or mum host group for any distinct sources. Then create a baby host group for every new report. This lets you simply monitor again each to the unique supply or the menace intelligence and determine which marketing campaign or menace actor is concerned. I like to incorporate a hyperlink to the supply within the host group description. That is particularly useful in case you are using a number of menace intelligence sources to your safety controls. Manage your host teams in a fashion that makes essentially the most sense to you.
You possibly can both create a brand new Customized Safety Occasion (see the primary a part of this weblog) for every baby host group with a definite identify or create one Customized Safety Occasion for the dad or mum host group with a generic identify. Both case can have you coated, and the host group identify within the alarm will show you how to rapidly determine the supply of menace intelligence.
Different Concerns
You all the time wish to carry out a Circulation Search (Examine -> Circulation Search) first earlier than constructing any Customized Safety Occasions. It will forestall you from flooding your self with alerts should you by accident embody the unsuitable IP tackle or are already frequently speaking with an IP tackle you propose to incorporate in a brand new host group.
We’d love to listen to what you suppose. Ask a Query, Remark Under, and Keep Linked with Cisco Safe on social!
Cisco Safety Social Channels
Share:
