Security

Security at 717 DEV

This page sets out how 717 DEV secures its own website, mail domain, and engagement data. The first section lists controls that anyone can verify from outside, with the method and the current result for each. The second lists operational commitments that cannot be observed externally.

Independently Verifiable

Externally observable

Each row gives the claim, how to check it, and the result. Results as of November 16, 2026.

Externally observable claims, how to check them, and the result
ClaimHow to checkResult
A strict Content Security Policy with no unsafe-inline on scripts or stylesHow to checkRead the response header.curl -sI https://717dev.com/ | grep -i content-security-policyResultscript-src 'self'
style-src 'self'
Trusted Types enforced, so the browser blocks scripts from writing raw HTML strings into the pageHow to checkRead the same header.curl -sI https://717dev.com/ | grep -i content-security-policyResultrequire-trusted-types-for 'script'
trusted-types 'none'
HSTSHow to checkcurl -sI https://717dev.com/ | grep -i strict-transport-securityResultHeader present
On the browser HSTS preload listHow to checkLook up 717dev.com at hstspreload.org.ResultPreloaded
Receiving servers are told to reject mail that fails authenticationHow to checkdig +short txt _dmarc.717dev.comResultp=reject
Only listed senders may send mail for this domainHow to checkdig +short txt 717dev.comResult-all
Only one certificate authority may issue certificates for this domainHow to checkdig +short caa 717dev.comResultdigicert.com
Framing protectionsHow to checkcurl -sI https://717dev.com/ | grep -i x-frame-optionsResultSAMEORIGIN
A Permissions-Policy that disables the APIs this site does not useHow to checkcurl -sI https://717dev.com/ | grep -i permissions-policyResultcamera=(), geolocation=(), microphone=() and more
No analytics and no advertising trackersHow to checkOpen the network panel in your browser and load any page.ResultEvery request on page load goes to 717dev.com
Contact form submissions go to this site, not to a third-party form serviceHow to checkRead the form-action and connect-src entries in the same Content Security Policy header, or the privacy policy.Resultform-action 'self' and connect-src 'self'
No cookies in normal operationHow to checkcurl -sI https://717dev.com/ | grep -i set-cookieResultNo output
Web fonts are self-hosted, so no third-party font provider receives a request when a page loadsHow to checkFilter the network panel to fonts.ResultEvery font comes from 717dev.com
A published vulnerability disclosure contactHow to checkOpen security.txt.ResultPublished, expires May 31, 2027
Downloadable artifacts have a published SHA-256 checksum, so you can verify them yourselfHow to checkFollow the steps below.ResultPublished for each PDF
Download Checksums

Verify a download

Each PDF on this site has its SHA-256 checksum published beside it, so you can confirm that your copy is the file we published.

  1. Check the file

    Download a PDF and its SHA-256 file to one folder, then run this there. It checks every PDF in the folder that has its SHA-256 file beside it.

    • SQL Injection: Fix & Prevent cheat sheetPDFSHA-256
    • Secrets Triage and Remediation cheat sheetPDFSHA-256
    shasum -a 256 -c 717dev-*.pdf.sha256
How We Handle Systems and Engagement Data

Documented operational commitments

These commitments cannot be verified from outside. If you are reviewing 717 DEV as a vendor, working with procurement sets them out alongside the agreements that bind them.

  • Multi-factor authentication and least privilege on administrative accounts
  • Mutual non-disclosure, with no expiration on confidentiality of sensitive material
  • Encrypted transport for everything sensitive
  • Engagement data stored with access limited to the engagement team, behind multi-factor authentication and least privilege
  • A documented handling and access trail for findings, reports, and supporting artifacts
  • Return or secure destruction of engagement data at closure, except where the law requires retention or you authorize it in writing
  • Current patching, change review, and monitoring on our own infrastructure
  • Inquiries stored on services that encrypt data at rest by default
  • Notification after a confirmed incident affecting personal information, within the timeframes the law requires

We apply the same web and mail hardening to our own domain that we recommend to clients.