Update AF templates and help #6949
Conversation
Signed-off-by: ricekot <[email protected]>
ricekot
force-pushed
the
auto/update-docs
branch
from
66891d3 to
60a9f7c
Compare
| deleteGlobalAlerts: true # Boolean, if true then will delete all existing global alerts, default false | ||
| alertFilters: # A list of alertFilters to be applied | ||
| - ruleId: # Int/String: Mandatory, the scan rule ID or the alert reference | ||
| - ruleId: # Int: Mandatory, the scan rule ID or the alert reference |
| the strings in the sites list is included. The sites list also supports | ||
| variables. | ||
|
|
||
| <H2>Job: outputSummary</H2> |
There was a problem hiding this comment.
This is not intended to be used by the user, it's an "internal" job to help the migration of the packaged scans to use the AF.
There was a problem hiding this comment.
This should be linked from somewhere (either other/main page or the TOC).
|
Great job! No new security vulnerabilities introduced in this pull requestUse @Checkmarx to reach out to us for assistance. Just send a PR comment with Examples: |
| <H2>YAML</H2> | ||
|
|
||
| <pre> | ||
| - type: wappalyzer # Passive scan wait for the passive scanner to finish |
There was a problem hiding this comment.
Maybe this is modelled based on another example but it just seems awkward to me.
If there's no good description for the job I think advice would be better handled as a note below or leading in.
Or maybe make sure the comment is clear that it's a note not a description? Just start it with # Note: and include the actual psw type/name?
4 participants
Ensure that templates and help are up to date with supported fields.