Skip to content

Collect the knowledge data from STUCCO demo using APIs provided by it.

Notifications You must be signed in to change notification settings

TheGodOfObelisk/GraphDataCollection

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

59 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

GraphDataCollection missions

  1. Collect the knowledge data from STUCCO demo using APIs provided by it.
  2. Collect the network security data from several websites using python crawlers.
  3. Store data collected in mission 2 in MYSQL database.
  4. Relation analysis.

Mission 1

Collect by type

Types available are listed below.
Account: An account on some specific system(s), either belonging to some specific user or a system account. All software runs as some account. All accounts are associated with a user or users (such as system accounts.)
Host: Any entity on the network, including PCs, routers, switches, virtual machines, etc.
Software: Any software components on a system, including OSes, applications, services, and libraries.
Vulnerability: A flaw in some software, that can cause improper, unintended operation, and can potentially be exploited as part of an attack.
Malware: Any malicious software. This can refer to either a stored binary or a running instance. Malware can contain code to launch an exploit. Malware can itself be an asset that an attacker uses in future attacks (eg. a backdoor left on a compromised system.) or can automatically launch additional attacks on behalf of the original attacker. Malware can be hosted by or communicate with servers controlled by the attacker. Malware can contain code to load other malware. Malware can reuse components from other malware samples.
IP: A specific IP address.
DNS Name: A DNS name (and possibly associated info - registration info, etc.).
Port: A specific network port.
Address: Any address (IP:Port), either inside or outside of the network.
Flow: A flow of traffic between two addresses.
Address Range: A range of IP addresses.

Data format

Store data in json-schema.

Mission 2

Url lists

Malwares:
https://www.symantec.com/security-center/a-z/A
Malicious domains:
http://www.malwaredomainlist.com/mdl2.php?search=&colsearch=All&quantity=All
NVD:
https://nvd.nist.gov/vuln/data-feeds
CNVD:
http://www.cnvd.org.cn/shareData/list

Data format

It is not recommended that we use GitHub to store backups and database dumps.

Malwares(Symantec)

Data is stored in json files. Each item has four basic records: title, link, description and pubDate. Other records are collected from web pages their links referring to.

Malicious domains

Data is stored in a csv file. Each record has six properties.

NVD

Data is stored in xml/json files. Because these files exceed GitHub's file size limit of 100.00 MB, they are not uploaded.

CNVD

Data is stored in xml files.

Mission 3

Use the file named "symantec_insert.py" to store data from symantec. The table structure is shown in "symantec.sql" file.
malware_init.py: store data into table Malware from symantec.
malware_os.py: analyze data in symantec and extract os information from it, update Edges and vertex tables. It refers to the relation of "malware affects os".
malware_cve.py: If refers to the relation of "malware exploits vulnerability". Vulneraility is indicated by CVE.

Mission 4

Initialize vulnerability table. Ensure that data is available to "malware_cve.py".
There are 3 steps to initialize vulnerability table. We divide vulnerabilities into 3 types. Type 1 indicates that NVD only and type 3 indicates CNVD only. Type 2 indicates that this entry is the output by combining NVD and CNVD entries. Type 2 records may have more than one CNVD id in its "cnvdId" column.
The "init.py" file is used to complete step 1. The "fusion.py" file is used to complete step 2. The "remain.py" file is used to complete step 3.

Mission 5

Analyze the output of Hone. Its format is pacpng. Unfortunately, it is difficult to analyze the output file of Hone. So I simply convert its format into "txt" using "tshark" command within the computer where Hone is configured in.

Command

Refer to the man-page of tshark to find suitable commands.
tshark -r [pcapng file] > [output file]
In Windows, we need to specify the accurate path of the tshark.exe file.
C:\Program Files\WireShark\tshark -r DESKTOP-AK8ARRP_20190603_144850.pcapng > "F:/test.txt"
We use the command below to specifiy the output directory.
honeutil read -d 'F:/'

Analyze

The field that we are most interested in is the summary information of processes or connections.
For example, "Process 736 exec'd C:\Windows\System32\lsass.exe as C:\windows\system32\lsass.exe" can offer us the name of the exe file, the number of its process and the path of the exe file.

Mission 6

Message Queue.

Mission 7

Local Bro Collector

Get traffic information from bro logs.
File "host-summary.log" stores the host information that collected by bro. Utilize this file through "broReader.bro".
Collect infomation for System, IP, Address, DNSName and relationships among them.
Consider adding Protocol to our ontology.

About

Collect the knowledge data from STUCCO demo using APIs provided by it.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published