Software Securityhome
Fix a findingSearch
Tag

AppSec programs

20 guides tagged AppSec programs, grouped by topic, with the SDLC phase and role each is written for.

SDLC phases
Roles

Application security

3 guides

Runtime, cloud & APIs

2 guides

Identity & cryptography

1 guide

Governance & frameworks

14 guides
Guide · Governance & frameworks

Start a minimal AppSec program with owners, triggers and metrics

Begin with ownership, a few risk-triggered activities, and evidence that findings are resolved; expand from demonstrated needs.

Security program · AppSec engineers, Security leaders

Guide · Governance & frameworks

Run an AppSec program: owners, finding states, deadlines and champions

Translate a security baseline into service ownership, change triggers, reusable patterns and evidence that work reaches deployment.

Security program · AppSec engineers, Security leaders

Guide · Governance & frameworks

Run an OWASP SAMM assessment with evidence and a practical roadmap

Use OWASP SAMM to distinguish isolated successes from repeatable practices and choose improvements the organization can sustain.

Security program · AppSec engineers, Security leaders

Guide · Governance & frameworks

Approve, expire and measure security exceptions without hiding risk

Keep temporary acceptance separate from remediation and measure outcomes using definitions that survive changing visibility.

Maintenance, Security program · Security leaders

Guide · Governance & frameworks

Cyber Resilience Act and payment pages: turn product-security obligations into an engineering evidence plan

Determine the relevant actor, product, market and requirement before connecting CRA or payment-security expectations to implementation work.

Planning, Maintenance, Security program · AppSec engineers, Security leaders

Guide · Governance & frameworks

Set remediation SLAs and measure AppSec outcomes

Set vulnerability SLAs by exploitation and exposure, route misses through expiring exceptions, and measure the program with cohort-based, censoring-aware metrics that resist gaming.

Maintenance, Security program · AppSec engineers, Platform engineers and SREs, Security leaders

Guide · Governance & frameworks

Build a runbook for CRA vulnerability and incident reporting

Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents through ENISA's Single Reporting Platform within 24 and 72 hours. Decide what is reportable, start the clock at the right moment, file through the platform and keep an evidence trail.

Maintenance, Security program · AppSec engineers, Security leaders

Guide · Governance & frameworks

Run a security champions program with protected time and outcome metrics

Put a trained engineer with protected hours in every in-scope team, write the role into a one-page charter, route sensitive changes and findings through champions and AppSec, and judge the program by coverage and outcomes instead of attendance.

Testing, Security program · AppSec engineers, Security leaders

Guide · Governance & frameworks

Prioritize vulnerabilities by exploitation, exposure and impact

Rank vulnerabilities with CISA KEV, EPSS, CVSS 4.0 vectors and SSVC decision points, adjust for presence, reachability and asset value, and turn the result into due dates. Covers NVD's 2026 enrichment changes and CISA BOD 26-04.

Maintenance, Security program · AppSec engineers, Security leaders

Guide · Governance & frameworks

Apply CISA Secure by Design: principles, pledge goals and evidence

What CISA's Secure by Design guidance and pledge ask of software manufacturers as of October 2026, and how to turn each of the three principles, the seven pledge goals and the Product Security Bad Practices into engineering actions, metrics and evidence.

Security program · AppSec engineers, Security leaders

Guide · Governance & frameworks

BSIMM vs SAMM vs SSDF: what each is for and which to use

How BSIMM16, OWASP SAMM 2.2.0 and NIST SSDF 1.1 differ, what each measures and does not, a chooser by situation, and a verified SSDF-to-BSIMM16-and-SAMM crosswalk with a script that reports evidence gaps.

Security program · AppSec engineers, Security leaders

Guide · Governance & frameworks

Run a developer security training program that changes code

Build role-based, hands-on developer security training from this site's learning paths, labs and fix cards, meet PCI DSS 6.2.2, NIST SSDF PO.2.2 and ISO/IEC 27001 A.6.3 with real evidence, and measure the effect with repeat findings instead of completion rates.

Security program · Developers, AppSec engineers, Security leaders

Guide · Governance & frameworks

Build an application security career: roles, skills, portfolio and certifications

The main application security role tracks (AppSec engineer, product security engineer, security champion, platform security engineer, security architect), the skills expected at each level, how to build a portfolio a hiring team can verify using this site's labs, projects and fix cards, and what common certifications do and do not show.

Security program · Developers, AppSec engineers, Security leaders

Guide · Governance & frameworks

UK Software Security Code of Practice: the 14 principles as engineering practice

What the UK government's voluntary Software Security Code of Practice (May 2025) asks of software vendors, each of its 14 principles mapped to engineering practice, NIST SSDF and the EU Cyber Resilience Act, and a CI check for the support-period principles.

Maintenance, Security program · AppSec engineers, Security leaders

All tags, lifecycle stages and roles

Find your next answer

Type to search. Search runs in your browser.

Searches run in your browser, but the host can infer them from the index files they load. The address shows your search so you can bookmark or share it.