717 DEV

Software security consulting: Assess it, fix it, prove it.

717 DEV works with organizations where software is the product or sits in the critical path. We assess applications, AI systems, and the programs behind them, build the fixes in your stack, and produce the evidence customers, regulators, and leadership ask for.

Core Practices

Three connected practices

Each practice answers a different question. Application & AI Security assesses the software, Security Engineering fixes it, and Software Security Assurance proves the program behind it. For how the pieces of the discipline fit together, see our guide to what software security is and how it is measured.

Is the software secure?

Application & AI Security

Find and reduce risk in the software itself.

  • Application Security Assessments
  • AI and LLM Security Reviews
  • Penetration Testing
  • Threat Modeling
  • and 4 more
Explore Application & AI Security
Can you prove it?

Software Security Assurance

Build a defensible software security program and prove that it operates.

  • Evidence Readiness Assessment
  • Secure Development Program Assessment
  • NIST SSDF Readiness
  • OWASP SAMM Assessment
  • and 10 more
Explore Software Security Assurance
Who builds the fix?

Security Engineering

Turn security recommendations into working controls.

  • DevSecOps Implementation
  • CI/CD Security
  • Security Automation
  • Remediation Engineering
  • and 6 more
Explore Security Engineering
Engagements

Selected engagements

Read each engagement in full
Flagship Assessment

Evidence of how your software is secured

Customers, regulators, and auditors ask organizations to show how their software is secured, usually on a deadline and often with a contract waiting on the answer. Owning security tools does not answer that question, and neither does a program that operates but cannot produce evidence that it does.

  • Enterprise customers
  • Regulators
  • Government purchasers
  • Executives
  • Boards
  • Auditors
  • Business partners

The Software Security Evidence Readiness Assessment examines how your organization governs, performs, and evidences software security across roughly thirty areas, from threat modeling and secure coding through SBOM processes, release integrity, and vulnerability disclosure. You get a scored picture, a gap analysis mapped to public frameworks, and a sequenced roadmap.

How the Work Fits Together

Scoped one at a time, designed to connect

We assess both the software and the program that produced it, can stay on to build the fixes, and validate every engagement before it closes. Each service is scoped and purchased individually, so a single penetration test can stand on its own.

Step 01

Assess

Test the product and examine the program behind it: architecture, code, pipelines, ownership, and the evidence sitting behind each control.

Step 02

Identify gaps

Distinguish controls that are missing from controls that exist but cannot be demonstrated, since each calls for a different fix.

Step 03

Implement

Build the controls, automation, and architecture changes in your stack, with tests, documentation, and handover.

Step 04

Validate

Re-test and re-examine each control, and close a gap only when there is evidence that the control operates.

  1. Application & AI SecurityIs the software secure?
  2. Software Security AssuranceCan you prove it?
  3. Security EngineeringWho builds the fix?

Validate, then start the next cycle from evidence

Findings inform the program view, the program view sets the order of the engineering work, and completed work returns for validation.
Get in Touch

Start a conversation

Whether you are scoping an assessment, preparing for a customer security review, or trying to determine where the gaps are, tell us about the situation.

A free scoping call of 30 to 45 minutes, no NDA required. We typically reply within 24 hours.