Skip to content
Vivanet

Security built into the system, not bolted on after.

Security as part of the architecture, the SDLC and the review loop. The failures we've seen were almost never the model; they were the access, the integration, or the audit trail.

What we do.

  • 01

    Security built in from day one

    Authentication, authorisation and encryption designed into product work from the start. The security review ends in approval, not a rewrite.

  • 02

    Threat modelling and secure architecture review

    Structured review of designs before they ship, with the finding bar set by what a motivated attacker would actually try, not a boilerplate checklist.

  • 03

    Architecture built for compliance audit

    SOC 2, ISO 27001, HIPAA, GDPR, PCI contexts: engineering choices made with the audit evidence in mind so the compliance work is observation, not creation.

  • 04

    Identity and access engineering

    Access models, role design, and the governance layer that makes least privilege a default rather than an aspiration.

  • 05

    Audit logging and detection

    Structured decision records across sensitive workflows, with the retention and query story worked out before an incident needs them.

  • 06

    Secure licensing for offline and regulated environments

    Cryptographic entitlement systems for software that runs in air gapped or regulated environments, where the usual phone home patterns are unusable.

What we actually use.

A working list.

  • OIDC / OAuth2
  • SAML
  • Vault
  • AWS KMS
  • Azure Key Vault
  • SOC 2 context
  • ISO 27001 context
  • HIPAA context
  • OpenPolicyAgent
  • SIEM integration
  • Burp Suite
  • OWASP ASVS

What people ask us.

  • What security engineering do you actually do?

    Security built in across product and platform, threat modelling, architecture made with the audit in mind, identity and access, and audit logging. We work alongside your security function, we don't replace it.

  • Do you do penetration testing?

    Penetration testing is a specialist discipline that is usually best done by a dedicated firm with an attack background. We help clients prepare for it, remediate findings from it, and build the engineering practice that reduces findings in future cycles.

  • Can you help with SOC 2 or ISO 27001?

    Yes, as engineering support in a compliance programme. The right architecture choices make the audit observation rather than creation. We work inside your compliance regime, not around it.

  • Can you join an existing security team?

    Yes. Talent augmentation into security teams is one of our common patterns, with engineers screened specifically for the discipline rather than placed from a generalist pool.

Have a security engineering need?

Tell us about it. We'll tell you honestly whether we have the right specialist, and what the shape of the engagement would look like.