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.

Sign up for GitHub

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

Update README.md #230

Merged
merged 1 commit into from
Sep 12, 2024
Merged

Update README.md #230

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions Scanner Vulnerabilities Report/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
If you are bringning data from multiple connectors and have locator order updated to merge assets and vulnerabilities, then scanner vulnerabilities from multiple connectors get tied to a single vulnerability ID.
In order to close the vulnerability in Kenna, scanner vulnerability from all the connector sources should get validated and closed.

This script helps to create a list of vulnerabilities which are kept open by one of the connector but closed by the other connector(s).
This script helps to create a list of vulnerabilities & the related assets which are kept open by one of the connector but closed by the other connector(s).
This can help you validate the scanning from the respective scanner keeping the detection open.

### Note:
Expand All @@ -16,7 +16,7 @@ python scanner_vuln_information.py
## Updates/Edits needed to execute the script

### 1: Update the base_url
By default, https://api.kennasecurity.com/ is being used. Update it to w.r.t your environment.
By default, https://api.kennasecurity.com/ is being used on Line # 17. Update it to w.r.t your environment.

### 2: API Key Token
Set an environment variable named KENNA_API_KEY with your actual API key as its value. The way you do this can vary depending on your operating system and the interface you're using (command line, graphical interface, etc.).
Expand All @@ -29,8 +29,8 @@ In macOS or Linux, you can set an environment variable in the terminal using the
*export KENNA_API_KEY=your-api-key*

### 3: Wait time for Export
By default the script waits for maximum time of 90 minutes to get the export from the customer's environment, in case your export is big and needs more time,
please update the *max_wait_time=5400* (in seconds) parameter on line #52 to accomodate your export.
By default the script waits for maximum time of 200 minutes to get the export from the customer's environment, in case your export is big and needs more time,
please update the *max_wait_time=12000* (in seconds) parameter on line #62 to accomodate your export.
Note: The scipt was tested with maximum time of 5400 seconds (90 minutes) with record count of ~24M and it executed successfully in 44 minutes.

## Requirements
Expand Down
Loading