Application Security Testing

Static analysis, dependency, secrets and dynamic scanning wired into your pipelines, with a triage policy, merge gates and review routines that keep findings actionable instead of ignored.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Application Security Testing, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Application Security Testing

Adding static analysis, dependency scanning and dynamic testing to development pipelines and triaging findings without drowning teams in noise.

  1. Application inventory and security testing risk tiers
  2. Baseline of security tests already running
  3. Static analysis tool selection
  4. First static analysis scan and accepted baseline
  5. Dependency scanning switched on for every repository
  6. Secrets scanning on new commits and full history
  7. Severity and triage policy for scanner findings
  8. Single findings tracker across all scanners
  9. Merge gate policy for security findings
  10. Weekly triage of new security findings
  11. False positive and suppression review
  12. Remediation deadline tracking by severity
  13. Scheduled full scans of default branches
  14. Scanner rule set tuning cycle
  15. Security testing metrics log
  16. Container image scanning in the registry
  17. Infrastructure as code security scanning in pull requests
  18. Quarterly scanner coverage audit
  19. Security champions findings clinic
  20. Reading a static analysis finding from source to sink
  21. OWASP Top 10 mapped to your scanner coverage
  22. Manual testing with an intercepting proxy
  23. Writing custom static analysis rules
  24. Prioritising findings with CVSS, EPSS and reachability
  25. Practice on a deliberately vulnerable application
  26. API security testing against the OWASP API Top 10
  27. Authenticated dynamic scanning of staging
  28. Reachability analysis to cut dependency alert noise
  29. SBOM generated for every release
  30. Fast feedback scans in the editor and pre-commit
  31. Open source toolchain versus commercial platform
  32. Automated fix suggestions trial
  33. Licence compliance policy in dependency scanning
  34. Security test plan for a new service before launch
  35. External penetration test scoping and follow-through
  36. Vulnerability disclosure programme launch
  37. Audit evidence pack for security testing controls
  38. Annual security testing programme review
  39. Free-tier security testing for a small team
  40. Rolling scanners out across many repositories
  41. Burning down an inherited backlog of old findings
  42. Mobile app security testing
  43. Security testing walkthrough for new engineers
  44. Security testing for a payments or regulated application
  45. Security regression tests from past findings
  46. Variant analysis after a confirmed vulnerability
  47. Coverage-guided fuzzing of parsers and input handlers
  48. Automated authorisation tests for every role
  49. Seeded vulnerability benchmark for your scanners
  50. Software supply chain checks on the build pipeline

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Application inventory and security testing risk tiers

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Scanners can only cover what someone has listed, and most teams discover forgotten repositories, internal tools and public APIs only after an incident.

First tasks

  • Export the list of repositories from your source control organisation
  • Match each repository to a deployed service and a named owning team
  • Mark internet exposure and the most sensitive data each application handles
  • Assign every application to tier one, two or three and share the list

Baseline of security tests already running

Before buying or adding anything, find out what is already switched on: a dependency bot someone enabled years ago, a linter with a few security rules, a scan nobody reads. A one-page baseline of tools, coverage and where their output goes stops duplicate purchases and shows the real gaps.

First tasks

  • Search pipeline configuration files for security scanning steps
  • Check repository settings for dependency and secrets alerts already enabled
  • Ask each team lead which scanner reports they actually read
  • Write the baseline table with coverage and gaps by testing type

Static analysis tool selection

Static application security testing tools differ far more in false positive rate and language support than their feature lists admit. Running two or three candidates on the same three repositories, one per main language, and counting true findings against noise gives a choice the team will actually keep using.

First tasks

  • Pick three repositories that represent your main languages and frameworks
  • Run each candidate tool on all three with default rules
  • Mark thirty sampled findings per tool as true or false positive
  • Record the chosen tool and the reasons in a short decision note

Make it yours.

Install Application Security Testing, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.