After creating an API specification scan in the Veracode Platform, you need to configure the scan with specific settings, such as the target API server, the server authentication method, and, if the server is behind a firewall, an Internal Scan Management (ISM) gateway.
Before You Begin
- You have a Veracode account with the Creator, Submitter, or Security Lead role. Any member of the team associated with the Dynamic Analysis is able to view the analysis and its results.
- You have created an API specification scan.
- Log in to the Veracode Platform.
- Select Scans and Analysis > Dynamic Analysis.
- In the All Dynamic Analyses table, locate the row for analysis that references the API specification you want to configure.
- In the Actions column, select Configure Analysis.
- In the API Specifications to Scan table, locate the row for the specification you want to configure.
- In the Actions column, click Configure (pencil icon) to open the Configure window.
In the API Specific Information section, from the Server dropdown menu, select the URL of the server you want to use with this specification.
OpenAPI 2.0 only supports a single server, while OpenAPI 3.0 and HAR files support multiple servers. You typically use these servers to select different environments, such as a production instance and a staging environment, or multiple production instances located in different regions.
Optionally, under the selected server URL, select the endpoints to include or exclude during scanning.
If you uploaded a HAR file that you captured using a browser, but have not filtered the HAR file, ensure that the server hosting your APIs is selected. API Scanning attempts to select the correct server based on traffic analysis, but you must confirm that the correct server is selected.
In the Authentication section, select Required to select and configure an authentication method for accessing the selected server.
- Under Additional Authentication Options, select the checkbox for one or more authentication options you want to use. See the table at the end of this topic for a description of each option.
- In the Internal Scanning section, if your scan uses an internal server that is not exposed to the public internet, you can configure Internal Scan Management (ISM) to enable access to that server. Select a configured ISM gateway and endpoint for accessing the server.
In the Advanced Options section, you can configure a custom user agent that API Scanning sends with each API request. By default, API Scanning identifies as the originator of the scan with
Veracode Security Scan/[email protected].
Compared to the substring for web application scanning, this substring does not include browser information. You can also use this substring to exempt Web Application Firewall (WAF) blocking or suppress pager notifications in an Intrusion Prevention System (IPS). See your vendor documentation for information about the solution for your organization.
Under Requests Per Second, select to allow an unlimited number of API requests or enter a limit.
Click Save to save the configuration. Depending on your scan configuration, a full Dynamic Analysis or prescan runs on the specified schedule.
|Client Certificate||Use for authenticating with servers configured with TLS authentication. API Scanning responds to any client certificate requests for certificates from a matching issuer with the configured certificate. The certificate file must be in PKCS#12 format, which usually has a
|Basic Authentication||Use basic and NTLMv2 authentication for authenticating with internal servers. API specifications that use basic authentication typically have
components: securitySchemes: basicAuth: type: http scheme: basic # specifies to use basic authentication.
|Custom Headers||Common type of authentication for use with Veracode API Scanning. You can define one or more name / value pairs. When defining the name, do not add any trailing colons. Values typically do not include a colon, but this is legal according to the RFC. These header names are reserved and cannot be used:
* Accept-Charset * Accept-Encoding * Access-Control-Request-Headers * Access-Control-Request-Method * Connection * Content-Length * Cookie * Cookie2 * Date * DNT * Expect * Host * Keep-Alive * Origin * Referer * TE * Trailer * Transfer-Encoding * Upgrade * Via
Custom headers in OpenAPI specifications are defined with the
openapi: 3.0.0 ... components: securitySchemes: ApiKeyAuth: # arbitrary name for the security scheme type: apiKey in: header # can be "header" or "cookie" name: X-API-KEY # name of the header, query parameter, or cookie
This example shows a JWT bearer token:
You can configure this token as a custom header with name
openapi: 3.0.0 ... components: securitySchemes: bearerAuth: # arbitrary name for the security scheme type: http scheme: bearer bearerFormat: JWT