Skip to content

Secure development

How Changineers implements the Secure Development Policy: design, build, review, ship.

The Secure Development Policy is published in the Changineers trust portal. This page is the handbook index for the procedures that implement it. The beliefs that underpin those procedures are on Engineering principles.

Engineering changes go through a design phase before code is written for non-trivial work, and reach main through pull requests with automated checks (tests, linting, dependency vulnerability scanning, secrets scanning). Application security testing combines static analysis on every PR with an external penetration test once a year. External researchers can report vulnerabilities through a published disclosure channel.

TopicPage
How features are scoped, drafted, and approved before code is writtenSolution design
Branch model, PR mechanics, CI gates, dependency and secret handlingShipping code
Annual external penetration testing and how findings are trackedPenetration testing
How external researchers can report security issuesResponsible disclosure