Objective 2.05 Explain the Process to Integrate and Configure Natively Supported Third-Party Vendors and Generic Formats with ASM (e.g., Difference Between Scanning Modes, iCAP) 303 Practice Questions (Page 4)

Questions 16–18

1. 16expert · hard

   A security engineer imports a scan result from a third-party scanner into ASM. The import is successful, but the engineer notices that the imported findings are not creating any learning suggestions. The policy is in 'Enforcement' mode with 'Learning' enabled. What is the most likely reason for this?

   • AThe imported findings are mapped to existing signatures, so no new learning suggestions are generated.
   • BThe policy is in 'Blocking' mode, which prevents learning suggestions from being generated.
   • CThe engineer did not enable the 'Generate Learning Suggestions' option during the import.
   • DThe scan result file did not include the necessary data for learning suggestions.
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   What happens to imported scan findings that do not match any ASM signature?

   • AThey are logged as errors
   • BThey are added as custom signatures
   • CThey are ignored
   • DThey are blocked by default
   Reveal Solution Discussion Select an answer first
3. 18application · medium

   A company uses Burp Suite Enterprise for web application scanning. The security team wants to import the scan results into ASM. What should the team do to prepare the Burp Suite output for a successful import?

   • AUpload the raw Burp Suite project file (.burp) directly.
   • BExport the findings as a Burp Suite XML file and upload it directly to ASM.
   • CManually enter the findings into ASM because Burp Suite is not supported.
   • DConvert the Burp Suite report to a generic XML format before uploading.
   Reveal Solution Discussion Select an answer first