 DAS scans can be run outside of the DevOps lifecycle. This is useful because we may not want to trigger a DAS scan each time the pipeline is run. We can also specify different environments or URLs for the DAS scanner to run on. Here, we give the scan a name. We can also provide a description. We can use or create a scanner profile. This gives us information as to how DAS is configured. We can also use or create a site profile. This tells us which URL to target. Then we go down and we click Save and Run Scan and we can see that DAS has been started. Now, we have dynamic application security testing running on our URL on demand. Scans can also be scheduled to run at configurable cadences.