# Security testing services: automated security checks for your application and its APIs

> Application Security Testing Services | Zapple.Tech. Canonical page: <https://zapple.tech/services/security-testing/>

When a customer asks how your application is tested for security, a one-off report ages quickly, so our security testing services are automated security testing that keeps running. We test your application and its APIs with static and dynamic checks, and with tests that try to reach what each role must not reach, wired into your CI so a weakness that comes back shows up on the next change. An engineer verifies every finding before it is reported, and the written scope says what was tested and what was not, so you have something specific to show. This is not a penetration test. We start with a one-week scope: what is tested, where, and by which checks.

## What you can order

- **Automated security checks in CI**: Checks that run on pull requests or nightly, next to your other tests, so a weakness that comes back shows up on the next change and not at the next audit.
- **API security testing**: Authentication, authorization per endpoint, input handling and data exposure in responses. Functional API tests of your rules are covered under API testing.
- **Access-rule tests for each role**: Tests that try to reach data or actions a role must not reach, for each main role, and across customer accounts if your product keeps them apart.
- **A verified findings report**: Each finding is checked by an engineer before it reaches the report, with severity, steps to reproduce and the evidence.

## Security testing services: what is in scope

Our application security testing services cover your application and its APIs, in a test environment, as written in the scope. The scope also says what is out of scope, and says it as plainly. Penetration testing, red-team exercises and social engineering are not part of this service, and nor are tests of physical or network infrastructure. If your customer or regulator names a standard, tell us. The scope says what the testing covers and what it does not.

The service is automated security testing: checks that keep running in your CI next to your other tests. A weakness that comes back shows up on the next change, not at the next audit. When you compare a security testing company with others, ask what keeps running after the report is delivered.

## Kinds of checks: static, dynamic and access-rule tests

- **Static:** analysis of your code and its dependencies without running the application.
- **Dynamic:** checks against a running application in a test environment.
- **Access-rule tests:** tests that try to reach data or actions a role must not reach, for example one customer's records from another customer's account.

The scope chooses which of these run. Scenarios we start from are simple ones: sign-ins with invalid credentials are refused, session and cookie handling behaves as specified, and the data a response exposes is the data it should.

## API security testing

For APIs the checks cover authentication, authorization per endpoint, input handling and data exposure in responses. Functional tests of your API rules, such as a user without a role getting a refusal, are written as ordinary tests; see [API testing](/services/api-server-side-test-automation/). Security testing looks for weaknesses nobody wrote a rule for. For web front ends, see [web test automation](/services/web-test-automation/).

## Automated security testing in your CI

This is DevSecOps testing in its plainest form. Checks run on pull requests or nightly, as agreed. New findings block the build or warn, as agreed. Known findings are tracked, not reported again every run, so the signal stays readable.

## How findings are verified and reported

Automated tools report false positives. An engineer checks each finding before it reaches the report. Each finding has a severity, steps to reproduce and the evidence. After a fix, the finding is retested.

## How we handle access and data

Testing happens in test environments, with test accounts. Credentials are issued by you. Nothing is pointed at production without written agreement. Only tools you approve are used, and nothing leaves your environment if your rules say so. For the tools survey, see [security testing tools](/blog/types-of-automation-testing/10-types-of-security-testing-tools/).

## What AI does and does not do in security testing

AI assistance is limited to drafting and repairing test code, and an engineer reviews each change before it is merged. People decide severity and what is reported. Testing AI features themselves is a different piece of work; see [security testing of AI chatbots](/services/ai-chatbot-testing/).

## When you need something other than this service

If you need a penetration test, a certification or a compliance audit, this is not it, and the scope week would tell you so. Automated checks also need a test environment to run against and someone on your side to receive findings and fix them; without either, set those up first. If you are not sure what to check first, a [QA audit](/services/audit-and-assessment/) looks at tests, pipeline and release process, and it says so when something else is needed. For behaviour under load, see [performance testing](/services/performance-testing/).

## From scope week to checks in your CI

1. **Security test scope:** about one week. The written scope, rules of engagement and a first verified findings list.
2. **Pilot:** two to six weeks. Checks in your CI, access-rule tests and a findings report.
3. **Ongoing:** checks keep running and fixes are retested, through [QA outsourcing](/services/qa-outsourcing/), a [dedicated QA team](/services/dedicated-qa-team/) or [engineers who join your team](/services/hire-test-automation-engineers/).

After each step you decide whether there is a next one. Prices are not published; send what the application does and the quote comes within one business day. Other test types are listed under [test automation services](/services/).

## What security testing does not solve

Security checks reduce the chance that a known kind of weakness ships. They do not prove that an application is secure.

- This is not a penetration test, a red-team exercise or a certification, and the report says so.
- Automated checks find known kinds of weakness, not every flaw in your business logic.
- A clean report means the agreed checks found nothing in the agreed scope. It does not mean the application is secure.
- Findings are fixed by your developers, and a retest confirms the fix.
- AI assistance writes and repairs test code. It does not decide severity or what is reported, and an AI draft of a check is reviewed by an engineer before it is merged.

## The three kinds of check the scope can choose from, what each does and what it works on.

| Check | What it does | What it works on |
| --- | --- | --- |
| Static | Analyses the code without running the application | Your code and its dependencies |
| Dynamic | Checks a running application | A test environment |
| Access-rule tests | Try to reach data or actions a role must not reach | Each main role, and across customer accounts if your product keeps them apart |

## How the work runs

1. **Security test scope** (About one week): We agree in writing what is in scope and what is not, the environments and test accounts, and the rules of engagement. We choose which kinds of checks run and why, and run the first automated checks against a test environment.
2. **Pilot** (Two to six weeks): Checks are wired into your CI and access-rule tests cover the main roles. Findings are reported with severity, steps to reproduce and evidence, and fixed findings are retested.
3. **Ongoing** (Monthly): The checks keep running on every change or nightly. A new finding is verified before it reaches you, and a fix is retested before it is closed. It runs under QA outsourcing, a dedicated QA team or engineers who join your team, whichever suits how you buy.

## FAQ

### What do security testing services include?

A written scope, automated checks against your application and its APIs, checks wired into your CI, and a report in which every finding was verified by an engineer. Which kinds of checks run is decided in the scope week, and the scope lists what is excluded.

### Is this a penetration test?

No. A penetration test is a separate exercise, and it is not part of this service. Here the aim is checks that keep running in your CI and a report of findings that an engineer has verified. The report states the limits of what was checked.

### What is the difference between SAST, DAST and IAST?

Static testing (SAST) examines code without running the program. Dynamic testing (DAST) probes a running application from the outside, without seeing its code, for example by sending malicious input. Interactive testing (IAST) tests the application while an automated test or a person uses it, through sensor modules included in the application code. This service uses static and dynamic checks; which ones run is decided in the scope week.

### Can security testing be automated?

The known kinds of weakness, yes, and the checks can run in your CI on every change. Flaws in business logic and the judgement of severity need people, which is why an engineer verifies each finding.

### Do you test APIs for security?

Yes, as part of the scope. The checks cover authentication, authorization per endpoint, input handling and data exposure in responses. Functional tests of your API rules are a separate piece of work, see API testing.

### How do you handle our credentials, data and production?

Tests run in test environments with test accounts. Credentials are issued by you, nothing is pointed at production without written agreement, and nothing leaves your environment if your rules say so. We do not fill in your security questionnaire for you, but the written scope and the report describe what was tested and what was not.

### Do you test AI features for prompt injection?

That is covered under security testing of AI chatbots, which has its own page and its own limits. This page covers the application and its APIs.

### Which tools and standards do you use?

The checks and tools are chosen in the scope week, with the reason written down, and only tools you approve are used. No standard is claimed on this page. If your customer or regulator names one, tell us, and the scope says what the testing covers and what it does not.

### How much does security testing cost?

Prices are not published. The quote depends on the scope, the number of roles and APIs, the environments and the CI set-up. Describe the application and you get a scoped quote within one business day.

[Request a security test scope quote](https://zapple.tech/services/security-testing/#start)
