Skip to content

Security research & engineering

AI security and engineering.

We build TAREOps for laboratory records and samples. Our engineering services help teams assess, build and harden AI systems that use sensitive data, tools and production workflows.

Tell us about the system and the decision. We’ll help agree the scope and the written outputs.

Our flagship product

TAREOps for laboratory records and samples.

TARE stands for Technical Analysis & Research Engine. TAREOps connects laboratory records, samples and materials, with design partner access for defined workflows.

Documentation assistance remains active R&D. Review the product maturity page for current capabilities and limits before planning a pilot.

Engineering services

Build it. Assess it. Improve it.

Choose a starting point based on the system and the decision in front of you.

Secure AI implementation

Build a useful workflow with controls from the start. We work on bounded AI workflows, model and tool integration, retrieval, access controls, evaluation, and the practices needed to run them.

Typical outputs

Agreed implementation, documented controls, evaluation results and handover.

Explore implementation

AI security assessments

Understand the risks before expanding access or relying on the output. We review agents, MCP integrations, retrieval systems and AI-assisted coding workflows, then explain the issues, their impact and the changes needed.

Typical outputs

Scoped findings, technical context and a prioritized remediation plan.

Compare assessment options

AI security remediation

Close the gap between a finding and a working fix. We make scoped changes to code, permissions, data boundaries, secrets handling, evaluation and operations, starting from our assessment or an existing report.

Typical outputs

Agreed changes, verification results, remaining issues and handover notes.

Explore remediation

We describe checks on our own implementation or remediation as verification or retesting. Independent assessment requires a separate scope and a conflict review.

Device & firmware security

When the question reaches the device itself.

Our OASIS lab supports device teardowns, component checks, firmware analysis and material comparisons. Stereo microscopy, electrical measurements, thermal imaging and FTIR help us answer a defined technical question. We agree the methods and handling before a device is sent.

Explore device assessments

Selected architecture, product-security and technical-risk questions also fit our technical review work.

How engagements work

Start with a question. Finish with usable work.

  1. Define the scope.

    Agree on the system, access, constraints, decision and outputs before work starts.

  2. Do the technical work.

    Build, assess or remediate within the agreed scope, documenting material changes and limits.

  3. Explain the result.

    Hand over the work, verification results, known limitations and next steps.

Read the approach

Before you engage

See what a review can produce.

The sample package uses a fictional system to show how scope, methods, findings and limitations are presented. Actual deliverables are agreed for your engagement.

About TKOResearch

Work directly with the person doing the work.

TKOResearch is led by Kevin O’Connor. The work combines hands-on security engineering, applied research and software development, with written findings and clear limits on what was tested.

Meet Kevin

Insights

Research and technical guides.

Start with guides to agent deployment, tool permissions and company document access.

Browse all articles

Discuss a project

What needs to be built, assessed or fixed?

Tell us about the system, the decision and the constraints. We’ll use an initial discussion to establish whether there is a useful scope of work.

Discuss a project