Engagement specific fields
Name | Description | |
---|---|---|
id | System generated, does not flow down | |
ID for the Engagement that shows up in children, not in any Enrichment indices.required: Yestype: keywordexample: <GUID> | ||
saltminer.engagement.publish_date | When engagement published Publish date required: No nullable type: timestamp example: 2020-11-02T23:57:04.344886 | |
saltminer.engagement.name | Engagement namerequired: Yestype: keywordexample: http://Saltminer.io Pentest 001 | |
saltminer.engagement.customer | Customer identifier for engagementrequired: Yes display name: Customer type: keyword example: ACME Fireworks Inc. | |
saltminer.engagement.summary | Summary description of the engagmentrequired: Yestype: text | |
saltminer.engagement.subtype | The sub-type for the engagement, for example this could be Mobile, Web, API or any other user defined value for the types of assessments that can be performed. display name: Subtype required: Yes type: keyword | |
saltminer.engagement.scan_id | Scan id that ties to this engagement. Because an Engagement (PenTest) is a special sort of assessment we treat it in may ways like a scan. This field points from the Engagement to it’s corresponding “scan” record”required: Yestype: keyword | |
saltminer.engagement .attachments[0].file_name | attachment file name (array)required: Notype: textexample: file.docx | |
saltminer.engagement .attachments[0].uri | attachment download uri (array)required: Notype: textexample: [guid].docx | |
saltminer.engagement.criticalsaltminer.engagement.highsaltminer.engagement.mediumsaltminer.engagement.lowsaltminer.engagement.info | System generated sum of open issues for the engagement/scan for this severityrequired: Yestype: integerexample: 100 | |
saltminer.engagement.attributes | objects |
Flow down fields #
Asset Inventory #
- saltminer.asset_inv.is_production
- saltminer.asset_inv.name
- saltminer.asset_inv.description
- saltminer.asset_inv.version
- saltminer.asset_inv.attributes
- saltminer.asset_inv.key