From e795741e53fad5d93f6727934d545ba390673f95 Mon Sep 17 00:00:00 2001
From: Prateek-Thakare A basic understanding of the above will simplify any new integrations with Mantis. Mantis Config file provides multiple customisations including: Once you have setup Mantis, you can now look at customising your scan requirements. Scan customisations are available via: INFO💡- Config File Path: /mantis/config/local.yml INFO💡: For more details on config.yml and how to edit it, Click here INFO💡: For more details on config.yml and how to edit it, Click here Mantis uses Ray framework to scale. Ray Core provides a small number of core primitives (i.e., tasks, actors, objects) for building and scaling distributed applications. Please Note - A short infrastructure setup is required before utilising this feature as described here Please Note - A short infrastructure setup is required before utilising this feature as described here The Mantis framework is designed to use Ray Core in the most efficient way, breaking down a single scan into the most granular level. To put it simply: INFO💡: For a more detailed understanding on how to integrate a new scanner, Click here INFO💡: For a more detailed understanding on how to integrate a new scanner, Click here INFO💡: For more details on config.yml and how to edit it, Click here INFO💡: For more details on config.yml and how to edit it, Click hereMantis folder structure - This will help you understand exactly where you need to make changes for new integrations
-
diff --git a/configuration/config-file.html b/configuration/config-file.html
index 7a4d2e0..f7ae48b 100644
--- a/configuration/config-file.html
+++ b/configuration/config-file.html
@@ -148,10 +148,10 @@
📋 Config File
-
diff --git a/configuration/configuration.html b/configuration/configuration.html
index 8aaf0b1..668170a 100644
--- a/configuration/configuration.html
+++ b/configuration/configuration.html
@@ -147,8 +147,8 @@ Mantis - Documentation
🛠️ Configuration
-
New Assets
Understanding config.yml
-
diff --git a/features/distributed_scanning.html b/features/distributed_scanning.html
index 562aa8c..2f926ce 100644
--- a/features/distributed_scanning.html
+++ b/features/distributed_scanning.html
@@ -157,7 +157,7 @@ 😃 Feature
How does Mantis distribute your scan ?
-
😃 Feature
-
diff --git a/features/workflow_customisation.html b/features/workflow_customisation.html
index e56b2ce..995d8e1 100644
--- a/features/workflow_customisation.html
+++ b/features/workflow_customisation.html
@@ -214,7 +214,7 @@ Example 2
Understanding config.yml
-
diff --git a/new-scanner-integrations/command-line-class.html b/new-scanner-integrations/command-line-class.html
index 066904c..b5ddea0 100644
--- a/new-scanner-integrations/command-line-class.html
+++ b/new-scanner-integrations/command-line-class.html
@@ -179,7 +179,7 @@ here, we are required to implement three functions:
Now that we have a clear understanding of the expected input and output from the tool, let's begin the process of creating the scanner class. As previously indicated here, we are required to implement three functions:
Info💡- As mentioned here, Mantis incorporates a range of pre-existing utility functions to facilitate the seamless integration of new tools
This function is required to parse what the scanner outputs and insert it into the database. In this context, a list of subdomains need to be extrated and inserted into the database.
-Info💡- To understand the DB schema, click here
+Info💡- To understand the DB schema, click here
def parse_report(self, outfile):
output_dict_list = []
@@ -241,7 +241,7 @@ here
+
Info💡- Depending on whether you are inserting an asset, or updating an asset for recon information, or adding a new finding, you can use the corresponding util functions as described here
⏭️ In a similar fashion let's try to add a new API scanner.
diff --git a/new-scanner-integrations/new-scanner-integration-api.html b/new-scanner-integrations/new-scanner-integration-api.html
index 2346e44..32a66f3 100644
--- a/new-scanner-integrations/new-scanner-integration-api.html
+++ b/new-scanner-integrations/new-scanner-integration-api.html
@@ -175,7 +175,7 @@ here, we are required to implement three functions:
+
Now that we have a clear understanding of the expected input and output from the tool, let's begin the process of creating the scanner class. As previously indicated here, we are required to implement three functions:
- get_api_calls()
- parse_reponse()
@@ -248,7 +248,7 @@ here
+
Info💡- Depending on whether you are inserting an asset, or updating an asset for recon information, or adding a new finding, you can use the corresponding util functions as described here
Let's now look at adding the new scanner to the config file.
diff --git a/print.html b/print.html
index 1252c19..aecf344 100644
--- a/print.html
+++ b/print.html
@@ -216,7 +216,7 @@ 😃 Feature
How does Mantis distribute your scan ?
Mantis uses Ray framework to scale. Ray Core provides a small number of core primitives (i.e., tasks, actors, objects) for building and scaling distributed applications.
-Please Note - A short infrastructure setup is required before utilising this feature as described here
+Please Note - A short infrastructure setup is required before utilising this feature as described here
The Mantis framework is designed to use Ray Core in the most efficient way, breaking down a single scan into the most granular level. To put it simply:
@@ -323,7 +323,7 @@ Example 2
-INFO💡: For more details on config.yml and how to edit it, Click here
+INFO💡: For more details on config.yml and how to edit it, Click here
-INFO💡: For more details on config.yml and how to edit it, Click here
+INFO💡: For more details on config.yml and how to edit it, Click here
-INFO💡: For a more detailed understanding on how to integrate a new scanner, Click here
+INFO💡: For a more detailed understanding on how to integrate a new scanner, Click here
Mantis provides multiple installation methods that includes performing the entire scan in a single system or multiple machines
@@ -524,8 +524,8 @@Once you have setup Mantis, you can now look at customising your scan requirements. Scan customisations are available via:
INFO💡- Config File Path: /mantis/config/local.yml
@@ -534,10 +534,10 @@Setup
Mantis Config file provides multiple customisations including:
-
- Workflow Customisation
-- Scheduler Customisation
-- Setting App Context
-- Slack Alerting
+- Workflow Customisation
+- Scheduler Customisation
+- Setting App Context
+- Slack Alerting
🎛️ Workflow Configuration
@@ -973,10 +973,10 @@Mantis folder structure - This will help you understand exactly where you need to make changes for new integrations -
Base scanner class - Based on the scanner that you want to integrate, this will help you choose the base class that you need to inherit -Important utility functions - If your new scanner only accepts IP addresses, TLDs, or sometimes both, you don't have to write any queries or functions to validate the inputs. Mantis has built-in utility functions that can provide you with this input directly. -DB models - After your new scanner completes its scan, you'll need to insert the results into MongoDB. To do so, you'll need to understand the schema that is in place. This will help you do that. +Mantis folder structure - This will help you understand exactly where you need to make changes for new integrations +Base scanner class - Based on the scanner that you want to integrate, this will help you choose the base class that you need to inherit +Important utility functions - If your new scanner only accepts IP addresses, TLDs, or sometimes both, you don't have to write any queries or functions to validate the inputs. Mantis has built-in utility functions that can provide you with this input directly. +DB models - After your new scanner completes its scan, you'll need to insert the results into MongoDB. To do so, you'll need to understand the schema that is in place. This will help you do that. A basic understanding of the above will simplify any new integrations with Mantis.
@@ -1254,7 +1254,7 @@-
Now that we have a clear understanding of the expected input and output from the tool, let's begin the process of creating the scanner class. As previously indicated here, we are required to implement three functions:
+Now that we have a clear understanding of the expected input and output from the tool, let's begin the process of creating the scanner class. As previously indicated here, we are required to implement three functions:
- base_get_commands() or get_commands()
- parse_report()
@@ -1280,13 +1280,13 @@here, Mantis incorporates a range of pre-existing utility functions to facilitate the seamless integration of new tools +
Info💡- As mentioned here, Mantis incorporates a range of pre-existing utility functions to facilitate the seamless integration of new tools
Implementing parse_report()
This function is required to parse what the scanner outputs and insert it into the database. In this context, a list of subdomains need to be extrated and inserted into the database.
-Info💡- To understand the DB schema, click here
+Info💡- To understand the DB schema, click here
def parse_report(self, outfile): output_dict_list = [] @@ -1316,7 +1316,7 @@
here +
Info💡- Depending on whether you are inserting an asset, or updating an asset for recon information, or adding a new finding, you can use the corresponding util functions as described here
⏭️ In a similar fashion let's try to add a new API scanner.
@@ -1352,7 +1352,7 @@here, we are required to implement three functions: +
Now that we have a clear understanding of the expected input and output from the tool, let's begin the process of creating the scanner class. As previously indicated here, we are required to implement three functions:
- get_api_calls()
- parse_reponse()
@@ -1425,7 +1425,7 @@here +
Info💡- Depending on whether you are inserting an asset, or updating an asset for recon information, or adding a new finding, you can use the corresponding util functions as described here
Let's now look at adding the new scanner to the config file.