Threat modelling before we build
Every feature starts with a short threat review: what could go wrong, who could abuse it, and how the design prevents it.
Unity Pulse Systems is a software house and a quality engineering and assurance company. We hold our own engineering to the standard we test yours against. This page sets out how we develop software securely, how we assure quality, and how we protect client systems and data.
When we build software — for clients or for ourselves — security is part of the process from the first design note, not a check at the end.
Every feature starts with a short threat review: what could go wrong, who could abuse it, and how the design prevents it.
Our standard: no code reaches a main branch without a second review, and the author never approves their own work.
Third-party packages are scanned on every build. Known critical flaws block the release until they're fixed or formally accepted.
Keys and credentials live in environment variables or a secrets manager — never in repositories, tickets or chat.
Tests, linting and security checks run in CI on every change. A failing gate stops the pipeline, not a person's judgement call.
Strict security headers, minimal non-root containers, least-privilege infrastructure and no unnecessary dependencies.
Our testing follows a defined method, so results are consistent, repeatable and defensible — whether they're read by your engineers, your board or a regulator.
We test deepest where failure costs most — mapped from your business risks, not from a generic checklist.
Every requirement links to its tests and every test to its evidence, so an auditor can follow the chain end to end.
Our standard: findings are checked by someone other than the person who built the change, so nobody signs off their own work.
Findings are rated on one published scale — impact and likelihood — so priorities are consistent across reports and teams.
Each finding comes with steps, environment, data and screenshots or logs, so your team can reproduce and verify the fix.
Exit criteria are agreed before testing starts. A release is signed off against them — not against a feeling.
You're giving us access to code and data that matter. These rules apply to every engagement.
A mutual NDA is signed before we see any code, data or architecture documents.
Read-only, time-limited credentials scoped to the systems under test. Access is revoked at the end of every engagement.
Wherever possible we test in your infrastructure, so production data never leaves your control.
We copy only what a test needs, and delete working copies within 30 days of engagement close.
Findings and evidence are shared through encrypted channels — never as plain email attachments.
Every engagement produces a documented trail of what was tested, how, and by whom.
Every company account — code repositories, cloud, email, password manager — requires MFA.
Access to client systems is granted per person, per engagement, reviewed while work is active and revoked on close.
Work devices use full-disk encryption, automatic updates and screen locks. Client data never goes on personal devices.
We produce the engineering and test evidence these frameworks expect. We are honest about where our role ends.
Our compliance line. We perform engineering gap analysis. We are not a Notified Body, we do not issue certification, and we do not give regulatory advice.
Isolate affected systems and revoke exposed credentials immediately.
Tell affected clients without undue delay — and within 72 hours of confirming an incident that involves their data.
Find the root cause, fix it, and verify the fix with the same rigour we apply to client systems.
Share a written post-incident report with what happened, the impact, and what changed to prevent it recurring.
If you believe you've found a security issue in one of our systems, email security@unitypulsesystems.com. We acknowledge reports within 2 working days and never take action against good-faith research.
We complete vendor security questionnaires and can share our working policies under NDA. Ask through the request form and tick "Send us an NDA first".