Security architecture that gets built, not just drawn.

Customer security requirements, AI-written code and the Cyber Resilience Act are raising the bar for software products. I join your team as a hands-on security architect: I design the security and build it with your developers.

Jarre Leskinen
Jarre Leskinen, CISSPProduct Security Architect

What product teams bring me in for

  • Customers and regulators are asking how secure your product is.

    Enterprise security reviews, questionnaires, ISO 27001, and now the Cyber Resilience Act.

    The fix

    I define your security architecture and build a development process where security is part of the work, so your answers describe how you really build software, and you can show it.

  • Your team ships faster with AI than security can keep up with.

    More code, agent integrations, and new authentication and authorisation paths.

    The fix

    Security has to be part of how features are designed and built, not a check at the end. I make it a natural part of your team's process, from design to release, so speed doesn't cost you control.

  • Nobody senior owns security.

    Security work lands on whoever has time, and a senior hire takes months to find.

    The fix

    I join your team for 3 to 12 months as its security architect or engineer. I own the priorities, build the controls with your developers, and leave the team able to carry them.

Security, built with your team.

I'm Jarre Leskinen, a product security architect working independently through Ingritia Oy. I help software product teams with application security, cloud and Kubernetes security, and customer identity.

I came to security from software engineering. That's why I start with your development process and your architecture, not just a checklist, and why every finding I hand over comes with a fix that fits your stack and the way your team works. I'd rather leave your team more capable than leave you a long report.

The name Ingritia comes from integrity. It's the part of this work I take most seriously.

Where I work

From application code down to the cloud, with a secure development process running through every layer.

  1. ApplicationWeb appsAPIsCI/CD pipelines
  2. IdentityCustomer loginOAuth 2.0 and OIDC
  3. PlatformKubernetesInfrastructure as code
  4. CloudAzureAWS
Across every layer

Secure SDLC

Threat modelling, code review and testing, built into CI/CD

How it starts

Most work is an embedded seat: I join your team as its security architect or engineer for 3 to 12 months, part-time or full-time. Some work starts smaller, with a scoped review of your application, cloud or customer login. Either way, the first step is a short call about what you're building.

  1. A short call

    About what you're building and what's worrying you or your customers.

  2. Scoped review

    Your application, cloud or customer login.

    Most work

    Embedded seat

    Your security architect or engineer for 3 to 12 months, part-time or full-time.

What an embedded seat ships in a quarter

Example
  1. Design review Threat model for the payment flow
  2. Team process Security review in the definition of done
  3. terraform/k8s Pod security and network policies
  4. auth-service Passkeys and safer account recovery
  5. docs/security Evidence pack for the customer security review

Security that helps your team ship, not stop.

Tell me what you're building: what the product is, what's worrying you or your customers, and when you'd like help. I usually reply within a working day.

Jarre Leskinen
Currently on an engagement, booking new work for 2027