> For the complete documentation index, see [llms.txt](https://asafahmadov.gitbook.io/devsecops/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asafahmadov.gitbook.io/devsecops/2.-approaching-automated-security-testing-in-devsecops/differentiating-the-pros-and-cons-of-automated-security-testing.md).
# Differentiating the Pros and Cons of Automated Security Testing
### Advantages of Automated Security Testing
▪ Scalable
▪ Repeatable
▪ Automatically block builds when tests fail (gating)
▪ Security becomes a habit, a standard in the development process
▪ Test results can change over time even if the code doesn’t change
### Disadvantages of Automated Security Testing
▪ Scans can take a long time
▪ Tools are generic
▪ False positives can get in the way
▪ Configuring and maintaining relevant tests is a continuous cost
▪ Security is not static, so test parameters should change over time
### When Automated Security Testing Is Useful
▪ Investment versus reward
▪ When delta scans are easy
▪ To comply with standards
▪ To get a security baseline
### When Automated Security Testing Is Less Useful
▪ Investment versus reward
▪ Complex business rules
▪ Fast-changing environments
▪ Mix of frameworks and languages
#### Some advice for using tools
▪ Use more than one tool for the same kind of test
▪ Let the team experiment with different tools
▪ Reporting format can make a difference
▪ Implement what works best for the team
▪ Facilitate, not mandate
▪ Know what to do with non-compliance results before implementing scans
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://asafahmadov.gitbook.io/devsecops/2.-approaching-automated-security-testing-in-devsecops/differentiating-the-pros-and-cons-of-automated-security-testing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.