Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Ability to Capture Malware Subject Evolution #98

Open
ikiril01 opened this issue Mar 2, 2015 · 2 comments
Open

Add Ability to Capture Malware Subject Evolution #98

ikiril01 opened this issue Mar 2, 2015 · 2 comments

Comments

@ikiril01
Copy link
Member

ikiril01 commented Mar 2, 2015

We should add the ability to more explicitly capture how a Malware Subject evolves over time. This can include some things that we currently express implicitly (e.g., changes in AV classifications over time), but there are likely components that would need to be made more explicit. For instance, a bot receiving a new configuration file and downloading a new payload is not something that we can currently capture. One possibility of achieving this is through timestamped relationships.

@ikiril01
Copy link
Member Author

Perhaps having timestamped relationships in combination with the ability to capture field data in the MalwareSubjectType is enough:

<Relationship type="downloads" timestamp="2015-03-16T09:30:10.5" source="malware_subject_1" target="malware_subject_2">

@ikiril01
Copy link
Member Author

This is primarily with regards to the evolution of malware Capabilities and Behaviors. In this regard, perhaps we should consider adding timestamps to these constructs:

<Capability id="capability-1" name="persistence" timestamp="2015-03-16T09:30:10.5"/>
<Behavior id="behavior-1" name="detect debugging" timestamp="2015-04-03T08:25:33.4"/>

Another possibility is to capture this implicitly through Analyses (something we already support):

<Analysis id="analysis-1" start_datetime="2015-04-03T08:25:33.4">
    <Entity_Reference entity_id="behavior-1"/>
</Analysis>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant