otx_transforms | Transforms for the AlienVault OTX service
kandi X-RAY | otx_transforms Summary
kandi X-RAY | otx_transforms Summary
otx_transforms is a Python library. otx_transforms has no bugs, it has no vulnerabilities and it has low support. However otx_transforms build file is not available. You can download it from GitHub.
Transforms for the AlienVault OTX service. First things first, you'll need to grab them from my Github. Once you grab the .mtz file, you'll open up Maltego, and then click on Import, then Import Configuration, then select the .mtz file you just downloaded from GitHub. You'll also need to download the Python file otx.py from GitHub into a place on your machine, something like /Users/Brian/Maltego or wherever you prefer. Once imported, you'll need to edit each one (a pain I know...) so it points to where the Python file you downloaded is located. To do this, open up "Manage Transforms" under the "Transforms" menu in the menubar. A window will pop like the screenshot below, in that window, you'll need to change the "Command Line" to wherever Python is, this will be different if you're using Windows. You'll also need to change the "Working Directory" to wherever the Python file otx.py is stored. To make things easier on people, these transforms can possibly be moved to a TDS server, so you don't need to do modify all the transforms, however, I didn't want to stand this up if a lot of people are using it, and it'll end up costing me a bunch of money to host the server. Also, some people would rather do things in-house, rather than having their queries going through a middle-man. After you have the transforms set up, you'll need to add your API key to the otx.py file in order to make the queries to AlienVault. Getting an API key is a painless process and just requires you to make an account in the OTX website. You'll need to edit Line 11 in the otx.py file with your key to use these transforms. Alright, good to go now, and we can start using these guys... Let's start by throwing out a IP Address we grabbed from malwaredomainlist.com, 213.145.225.170. Pretty boring right now, so, let's start adding some basic context around this indicator. Right-click on the IP and then select the "OTX - Get ASN/Geo Data" to run the transform that pulls the geographic and ASN data from AlienVault OTX. Once you run the transform, you get a new Location entity that contains the ASN and Country associated with that IP Address. Alright, let's dig a little deeper. The next transform available to us is "OTX - Get Associated Malware". Running this will create Malware entities in your graph, that are hashes associated with the given entity. In the above image, we can see two hashes that are associated with this IP Address. Before digging into the hashes, let's see what else we can figure out about this IP Address... Let's right-click on the IP Address and choose "OTX - Get Passive DNS". This will query OTX and return any domains that this IP has resolved to in the past. You'll also notice that the link between the IP and the hashes as well as any other links (excluding ASN/Geo data), will show the date that the link was seen. For instance, the dates in the links below show the date that the domains were seen resolving to that IP Address. Alright, next for the IP Address is seeing what other "Pulses" were related to this indicator. Pulses are a collection or group of indicators that users of OTX can submit to group related indicators together. If we right-click and select the "OTX - Get Related Pulses", we'll see a new entity type called "Pulse" be displayed for related indicators. You'll see in the bottom of the image above, the little green alien with the title being the Pulse name "MalwareDomainList", which is where we grabbed the initial indicator from. Lastly for this indicator is related URL's. This consists of any URL's seen for any of the domains that this IP resolved to in the past. Right click on the indicator and select "Get Related URL's" to get started. That's it for this type of indicator. You can use most of the above transforms for other indicator types as well, such as Domains, Hostnames, URL's and Hashes, so try it out on all of them. Next, I want to cover some other transforms that are available for certain entity types, first up is Hashes. If you right-click on a hash, you'll have the new transform "OTX - Get File Analysis" available to you. Clicking on this will create a new entity with the MD5 hash of the file you selected. If you then click on "Type Actions" when you right-click, and then "Open all URLs" you can then open a new page in your browser to the analysis of the file hash. Last thing to cover is viewing indicators associated with a particular pulse. If we right-click on the pulse entity, we can use the new transform "OTX - Get Related Indicators" to return any indicators associated with this pulse. There is a small bug currently, where if the indicator type isn't one supported by Maltego, it will display the default chess icon. I'll work on making sure all that can be supported by Maltego, are supported. Alright, well, that should cover everything. For questions, feel free to email me at brian@nullsecure.org or post any issues/bugs to the Github page.
Transforms for the AlienVault OTX service. First things first, you'll need to grab them from my Github. Once you grab the .mtz file, you'll open up Maltego, and then click on Import, then Import Configuration, then select the .mtz file you just downloaded from GitHub. You'll also need to download the Python file otx.py from GitHub into a place on your machine, something like /Users/Brian/Maltego or wherever you prefer. Once imported, you'll need to edit each one (a pain I know...) so it points to where the Python file you downloaded is located. To do this, open up "Manage Transforms" under the "Transforms" menu in the menubar. A window will pop like the screenshot below, in that window, you'll need to change the "Command Line" to wherever Python is, this will be different if you're using Windows. You'll also need to change the "Working Directory" to wherever the Python file otx.py is stored. To make things easier on people, these transforms can possibly be moved to a TDS server, so you don't need to do modify all the transforms, however, I didn't want to stand this up if a lot of people are using it, and it'll end up costing me a bunch of money to host the server. Also, some people would rather do things in-house, rather than having their queries going through a middle-man. After you have the transforms set up, you'll need to add your API key to the otx.py file in order to make the queries to AlienVault. Getting an API key is a painless process and just requires you to make an account in the OTX website. You'll need to edit Line 11 in the otx.py file with your key to use these transforms. Alright, good to go now, and we can start using these guys... Let's start by throwing out a IP Address we grabbed from malwaredomainlist.com, 213.145.225.170. Pretty boring right now, so, let's start adding some basic context around this indicator. Right-click on the IP and then select the "OTX - Get ASN/Geo Data" to run the transform that pulls the geographic and ASN data from AlienVault OTX. Once you run the transform, you get a new Location entity that contains the ASN and Country associated with that IP Address. Alright, let's dig a little deeper. The next transform available to us is "OTX - Get Associated Malware". Running this will create Malware entities in your graph, that are hashes associated with the given entity. In the above image, we can see two hashes that are associated with this IP Address. Before digging into the hashes, let's see what else we can figure out about this IP Address... Let's right-click on the IP Address and choose "OTX - Get Passive DNS". This will query OTX and return any domains that this IP has resolved to in the past. You'll also notice that the link between the IP and the hashes as well as any other links (excluding ASN/Geo data), will show the date that the link was seen. For instance, the dates in the links below show the date that the domains were seen resolving to that IP Address. Alright, next for the IP Address is seeing what other "Pulses" were related to this indicator. Pulses are a collection or group of indicators that users of OTX can submit to group related indicators together. If we right-click and select the "OTX - Get Related Pulses", we'll see a new entity type called "Pulse" be displayed for related indicators. You'll see in the bottom of the image above, the little green alien with the title being the Pulse name "MalwareDomainList", which is where we grabbed the initial indicator from. Lastly for this indicator is related URL's. This consists of any URL's seen for any of the domains that this IP resolved to in the past. Right click on the indicator and select "Get Related URL's" to get started. That's it for this type of indicator. You can use most of the above transforms for other indicator types as well, such as Domains, Hostnames, URL's and Hashes, so try it out on all of them. Next, I want to cover some other transforms that are available for certain entity types, first up is Hashes. If you right-click on a hash, you'll have the new transform "OTX - Get File Analysis" available to you. Clicking on this will create a new entity with the MD5 hash of the file you selected. If you then click on "Type Actions" when you right-click, and then "Open all URLs" you can then open a new page in your browser to the analysis of the file hash. Last thing to cover is viewing indicators associated with a particular pulse. If we right-click on the pulse entity, we can use the new transform "OTX - Get Related Indicators" to return any indicators associated with this pulse. There is a small bug currently, where if the indicator type isn't one supported by Maltego, it will display the default chess icon. I'll work on making sure all that can be supported by Maltego, are supported. Alright, well, that should cover everything. For questions, feel free to email me at brian@nullsecure.org or post any issues/bugs to the Github page.
Support
Quality
Security
License
Reuse
Support
otx_transforms has a low active ecosystem.
It has 32 star(s) with 9 fork(s). There are 6 watchers for this library.
It had no major release in the last 6 months.
There are 6 open issues and 0 have been closed. On average issues are closed in 1261 days. There are 1 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of otx_transforms is current.
Quality
otx_transforms has 0 bugs and 0 code smells.
Security
otx_transforms has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
otx_transforms code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
otx_transforms does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
otx_transforms releases are not available. You will need to build from source code and install.
otx_transforms has no build file. You will be need to create the build yourself to build the component from source.
otx_transforms saves you 108 person hours of effort in developing the same functionality from scratch.
It has 275 lines of code, 25 functions and 2 files.
It has high code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of otx_transforms
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of otx_transforms
otx_transforms Key Features
No Key Features are available at this moment for otx_transforms.
otx_transforms Examples and Code Snippets
No Code Snippets are available at this moment for otx_transforms.
Community Discussions
No Community Discussions are available at this moment for otx_transforms.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install otx_transforms
You can download it from GitHub.
You can use otx_transforms like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.
You can use otx_transforms like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page