About — InferLabs Pty Ltd, Australia

We built the tools we kept wishing existed.

We have led security inside some of the largest and most scrutinised organisations in the country, and spent a lot of that time working around tooling that made the job harder. Bloated processes, scanners that cried wolf, assessments that were mostly document handling. InferLabs exists to fix the specific things we found broken.

01 — Why we started

No buzzwords. The problems were specific.

Between us we have run security programs at Amazon, Cisco, Macquarie and NAB, and worked across Australian government. Different sectors, same three complaints: the scanner produced more noise than signal, the assessment took three times as long as the assessing, and the controls everyone relied on were the ones nobody could actually verify.

Then agents arrived and quietly changed the shape of the problem. Software is now written and increasingly run by systems that hold real credentials and act on their own reasoning, at a rate no review process was designed to absorb. The honest response is not to slow it down. It is to move the controls to where the work now happens.

So we build in that seam: a vault that lets an agent use a credential it can never read, and an assessment platform that emits its own evidence instead of a separate reporting exercise. Small tools with clear boundaries, for teams that take this seriously.

02 — How we build

Five commitments we are willing to be held to.

Controls belong in the path

A control that sits beside the work is documentation. A control the work has to pass through is a control. Everything we ship is built to stand in the execution path and be honest about what it catches when it does.

Say what it does not do

Every one of our products has a boundary, and we would rather write it on the page than let someone discover it in an incident. Security tools that oversell are how people end up unprotected while feeling covered.

Local by default

The default should be that your data stays on your machine and in your environment. Sending it somewhere is a decision you make deliberately, not the price of using the tool.

Readable where it counts

When the argument for a tool is trust, the source has to be available and small enough to actually read. Assertion is not evidence.

Australian context, properly

Essential Eight, the ISM and IRAP are not a compliance checkbox bolted onto a US product. We have been assessed and we have assessed, and the tooling reflects what those regimes really ask for.

03 — Who we are

Two founders, both practitioners.

Tanim Rahman

Tanim Rahman

Co-Founder & CEO

Shaped security programs at Amazon, Cisco and in government. Spends his time turning hard-won lessons about what actually holds up under scrutiny into tools that are small enough to trust.

Miles Poppleton

Miles Poppleton

Co-Founder & CTO

Built platform and architecture at Macquarie and NAB and across government programs. Full-stack and systems engineer, responsible for the parts of our products that have to be correct rather than merely convincing.

Security lead, developer, or someone with an awkward question?