Unity Pulse Systems Submit a request
Trust Center

How we build, test and protect what you trust us with.

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.

01 · As a software house

Secure development, by default

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.

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.

Peer review on every change

Our standard: no code reaches a main branch without a second review, and the author never approves their own work.

Dependency & vulnerability scanning

Third-party packages are scanned on every build. Known critical flaws block the release until they're fixed or formally accepted.

Secrets never in code

Keys and credentials live in environment variables or a secrets manager — never in repositories, tickets or chat.

Automated quality gates

Tests, linting and security checks run in CI on every change. A failing gate stops the pipeline, not a person's judgement call.

Hardened by default

Strict security headers, minimal non-root containers, least-privilege infrastructure and no unnecessary dependencies.

02 · As a quality engineering & assurance company

Quality you can audit

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.

Risk-based test planning

We test deepest where failure costs most — mapped from your business risks, not from a generic checklist.

Requirements-to-evidence traceability

Every requirement links to its tests and every test to its evidence, so an auditor can follow the chain end to end.

Independent verification

Our standard: findings are checked by someone other than the person who built the change, so nobody signs off their own work.

A defined severity model

Findings are rated on one published scale — impact and likelihood — so priorities are consistent across reports and teams.

Documented, reproducible evidence

Each finding comes with steps, environment, data and screenshots or logs, so your team can reproduce and verify the fix.

Clear release sign-off criteria

Exit criteria are agreed before testing starts. A release is signed off against them — not against a feeling.

03 · Client data handling

Your systems and data stay yours

You're giving us access to code and data that matter. These rules apply to every engagement.

NDA before access

A mutual NDA is signed before we see any code, data or architecture documents.

Least-privilege access

Read-only, time-limited credentials scoped to the systems under test. Access is revoked at the end of every engagement.

Work inside your environment

Wherever possible we test in your infrastructure, so production data never leaves your control.

Data minimisation & deletion

We copy only what a test needs, and delete working copies within 30 days of engagement close.

Encrypted by default

Findings and evidence are shared through encrypted channels — never as plain email attachments.

Audit-ready records

Every engagement produces a documented trail of what was tested, how, and by whom.

04 · Access & devices

Who can reach your systems — and how

Multi-factor authentication everywhere

Every company account — code repositories, cloud, email, password manager — requires MFA.

Access per engagement

Access to client systems is granted per person, per engagement, reviewed while work is active and revoked on close.

Managed, encrypted devices

Work devices use full-disk encryption, automatic updates and screen locks. Client data never goes on personal devices.

05 · Compliance scope

The frameworks we work with

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.

  • GDPR — privacy by design in everything we build and test
  • IEC 62304 / ISO 13485 — test evidence for medical software
  • EU AI Act — testing evidence for AI systems
  • Working practices modelled on SOC 2 and ISO 27001 controls
  • Saudi PDPL and UAE data-protection awareness for MENA clients
06 · Incident response

If something goes wrong, you'll hear it from us first

  1. 01

    Contain

    Isolate affected systems and revoke exposed credentials immediately.

  2. 02

    Notify

    Tell affected clients without undue delay — and within 72 hours of confirming an incident that involves their data.

  3. 03

    Investigate & fix

    Find the root cause, fix it, and verify the fix with the same rigour we apply to client systems.

  4. 04

    Report

    Share a written post-incident report with what happened, the impact, and what changed to prevent it recurring.

07 · Responsible disclosure

Found a vulnerability? Tell us.

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.

Please include
  • Where you found it (URL or system)
  • Steps to reproduce
  • The impact you believe it has
  • How we can reach you
Please don't
  • Access, change or delete data that isn't yours
  • Run denial-of-service or social-engineering tests
  • Disclose publicly before we've fixed it
Due diligence

Need more for your security review?

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".

Contact us