From 245bc7fe8c4ebe789555f49b45ab797131908dd7 Mon Sep 17 00:00:00 2001
From: FPolillo <128715222+FPolillo@users.noreply.github.com>
Date: Fri, 13 Oct 2023 13:09:10 -0700
Subject: [PATCH] Update readme with Skip_autoclose and
 Ignore_scanner_last_seen_time Settings

This is an updated requested by Yi Chen Cheng, in ticket TD-302.
---
 tasks/connectors/aws_inspector2/readme.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/tasks/connectors/aws_inspector2/readme.md b/tasks/connectors/aws_inspector2/readme.md
index a916d931..3a66d9f2 100644
--- a/tasks/connectors/aws_inspector2/readme.md
+++ b/tasks/connectors/aws_inspector2/readme.md
@@ -2,6 +2,11 @@
 
 This task brings in asset and vulnerability data from AWS Inspector V2.
 
+## Skip_autoclose and Ignore_scanner_last_seen_time Settings
+**Skip_autoclose**: This setting's default is set to **True**. In some cases, you may need change the skip_autoclose default to close specific vulnerabilities. To change it, in the JSON or source code, change the skip_autoclose to **False**.
+
+**Ignore_scanner_last_seen_time**: This setting's default is set to **False**. When it imports the data, it uses the scanners' reported time, instead of the time of the connector's last run, so it may cause an issue if you have an asset inactive-limit shorter then the frequency of your scans. For example, if you have an asset inactive limit set to 2 days, but you scan assets every 5 days, assets are then set to inactive. To solve this issue, change the ignore_scanner_last_seen_time to **True** so the assets_last_seen_time is set to when the connector runs. Currently, this setting only exists in backend administration. For help, contact **support**.
+
 ## Running the task
 
 See the main toolkit README for instructions on running tasks. For this task, if you leave off the Kenna API Key and Kenna Connector ID, the task will create a json file in the default or specified output directory. You can review the file before attempting to upload to the Kenna API.