actions-marketplace-validations/HCL AppScan Dynamic Analyzer
Scan for security issues in web applications
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| baseurl | baseURL of ASOC API | yes | https://cloud.appscan.com |
| asoc_key | API key for connecting to ASoC. | yes | — |
| asoc_secret | Secret for connecting to ASoC. | yes | — |
| application_id | The ASoC application id where your scan will appear. | yes | — |
| scan_name | The name of the scan created in ASoC. | no | — |
| scan_type | The type of scan - staging or production | no | staging |
| dynamic_scan_type | Choose between dast or upload. DAST will require you to specify starting URL and login, while upload will only require you to specify a .scan or .scant file | yes | dast |
| scan_or_scant_file | If dynamic_scan_type is set to "upload", then you will need to provide the .scan or .scant file here | no | — |
| starting_URL | The starting URL of the DAST scan | no | https://demo.testfire.net?mode=demo |
| login_method | Login Method of the scan, can be none, userpass, or recorded | no | none |
| optimization | Optimization level: NoOptimization, Fast, Faster, Fastest | no | Fastest |
| network | Set the type of network, if this is set to private, you must have AppScan Presence created in advance | no | public |
| presence_id | Provide the appscan presence ID here | no | — |
| ephemeral_presence | If set to true, this action will deploy a ephemeral (temporary) instance of the AppScan Presence on the runner. Please take note that this will ignore presence_id and network settings, and will force set wait_for_analysis to true | no | false |
| login_user | if login_method is userpass, provide the username here | no | — |
| login_password | if login_method is userpass, provide the password here | no | — |
| login_sequence_file | Provide a path to the Login Traffic File data. Supported file type: CONFIG: AppScan Activity Recorder file | no | — |
| email_notification | Send email notification uponn scan completion | no | false |
| personal_scan | set to personal scan | no | false |
| wait_for_analysis | Set this true to wait for analysis to complete before finishing job. | yes | true |
| wait_for_analysis_timeout_minutes | maximum duration in minutes before the job will no longer wait and proceeds to complete, default is 360 (6 hours) | no | 360 |
| fail_for_noncompliance | If **fail_for_noncompliance** = true, fail the job if any non-compliant issues are found in the scan | no | false |
| fail_by_severity | If **fail_by_severity** is set to true, failure_threshold must also be set. This will fail the job if any issues equal to or higher (more severe) than failure_threshold are found in the scan. | no | false |
| failure_threshold | If **fail_for_noncompliance** is enabled, the severity that indicates a failure. Lesser severities will not be considered a failure. For example, if failure_threshold is set to Medium, Informational and/or Low severity issues will not cause a failure. Medium, High, and/or Critical issues will cause a failure. | no | High |
Outputs
no outputs