Engagements
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: Yes type: keyword example: <GUID> |
|
| saltminer.engagement.publish_date |
When engagement published required: No nullable type: timestamp example: 2020-11-02T23:57:04.344886 |
| saltminer.engagement.name |
Engagement name required: Yes type: keyword example: http://Saltminer.io Pentest 001 |
| saltminer.engagement.customer |
Customer identifier for engagement required: Yes type: keyword example: ACME Fireworks Inc. |
| saltminer.engagement.summary |
Summary description of the engagment required: Yes type: 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. 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: Yes type: keyword |
| saltminer.engagement .attachments[0].file_name |
attachment file name (array) required: No type: text example: file.docx |
| saltminer.engagement .attachments[0].uri |
attachment download uri (array) required: No type: text example: [guid].docx |
|
saltminer.engagement.critical saltminer.engagement.high saltminer.engagement.medium saltminer.engagement.low saltminer.engagement.info |
System generated sum of open issues for the engagement/scan for this severity required: Yes type: integer example: 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