You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add the ability to capture the beaconing/callout/C2 Domains used by a malware instance, either as part of a Capability or a separate structure.
The text was updated successfully, but these errors were encountered:
An important aspect of this is capturing information about network infrastructure associated with operationalizing and delivering the malware instance. This would likely involve:
Hostnames used
Associated ASNs
Associated IPs (especially with regards to DNS resolution)
Update: it would also be useful to capture the nature or type of server being used, e.g.,
For C2 and Exfiltration entities, it may make the most sense to define this as a structured Capability property that references existing Objects (such those originating from Actions).
As far as other entities related to malware distribution/origination network infrastructure, I'm wondering if this is more aligned with malware field data (which we already capture to some extent, though it will be refactored per #95), and thus should be captured there? E.g.,
We should add the ability to capture the beaconing/callout/C2 Domains used by a malware instance, either as part of a Capability or a separate structure.
The text was updated successfully, but these errors were encountered: