Skip to main content

About Tricognita

Built to close the gap between finding a security problem and knowing it is fixed.

Tricognita is a cloud security engineering company, built from India and serving India and the United Arab Emirates. We combine hands-on security engineering with ARIA, our product for cloud control remediation and verification.

Our story

Why Tricognita exists

Nithish Kumar S

Founder & Security Engineer — Tricognita

Credentials and focus

Building secure SaaS products made one problem clear to me: security work often ends with a findings list. The issues get identified, but fixing them, verifying the result and keeping those controls in place still takes repeated manual effort.

Findings pile up, fixes are not always proven, and controls can quietly break again. I built Tricognita around closing that loop, Test → Fix → Verify → Keep secure, rather than stopping at the report.

That is why Tricognita has two parts. Our services solve real customer security problems and show which workflows and fixes are safe to repeat. ARIA turns those repeatable parts into software, so there is less repetitive work, while people stay responsible for judgement, sensitive decisions and customer context.

ARIA was built to turn repeated cloud security work into a repeatable verification and remediation workflow, with the customer approving every change.

— Nithish Kumar S

Company model

Two engines: services and product

Both are core to Tricognita, and each makes the other better.

Services

What our people do

Assessment, testing, remediation, readiness and secure engineering, with retainers that keep controls in place.

Our services

Product

ARIA

Automates the repeatable work: evaluating controls, approved bounded fixes, verification, re-checks and records. Every change needs the customer's authorization.

See ARIA

How we operate

What we do differently

  • A written scope first

    Every engagement starts with a scoping call and a written scope before any work begins.
  • Nothing changes without authorization

    A named person in the customer's organisation approves every change, and each change is bounded to what it fixes.
  • Every fix is verified

    Work is finished when the check passes, not when a change is made.
  • Service work becomes product

    Fixes that prove safe and repeatable in engagements are built into ARIA.

Engineering principles

How we make security changes

  • Authorization before change

    Nothing in a customer's cloud changes without approval from a named person in their organisation.
  • Bounded remediation

    Each change is scoped to the resource and the control it fixes, with a plan to roll it back.
  • Verification, not assumption

    A fix counts only when the check that found the problem passes on the same resource.
  • Evidence and traceability

    Checks, approvals and changes are recorded, so anyone reviewing the work can follow what happened.
  • Least-privilege access

    Checking uses read-only access. Changing needs a separate, narrow permission the customer grants and can remove.
  • Cloud-aware engineering

    AWS, Azure and Google Cloud each work differently. Controls are checked and fixed the way each cloud actually behaves.
  • People decide what matters

    Judgement on risk, priority and sensitive production changes stays with people, never with software alone.

Founder

Nithish Kumar S

Founder & Security Engineer — Tricognita

Focus

  • Cloud security engineering
  • AWS and Microsoft Azure security
  • Designing and building ARIA
  • Security automation
  • DevSecOps and secure deployment
  • Full-stack engineering
  • Linux and security tooling

Individual credentials

  • AWS Certified Solutions Architect – Professional
  • AWS Certified Security – Specialty
  • Quick Heal Digital Forensics & Incident Response (DFIR)
  • CompTIA Network+
  • Red Hat System Administration I (RH124)

These are the founder's personal credentials, not company certifications.

Our product

ARIA

Cloud control remediation and verification

We built ARIA so the repeatable parts of cloud security work are done the same way every time, with customer approval and human judgement kept in the loop.

LaunchingHow ARIA works

Where we are building

India and the United Arab Emirates

  • India

    Our first commercial base. Tricognita is being built from India, and we work directly with Indian SaaS, technology and security teams.

    Cloud security engineering for Indian SaaS, fintech and technology teams preparing for enterprise customer reviews, ISO 27001 or SOC 2 audits and regulator expectations.

  • United Arab Emirates

    Part of our target market from the start. Tricognita is built to serve cloud-driven businesses beyond one geography, and the UAE is an important regional market.

    The same engineering, scoping and approval model for UAE companies running on AWS and Microsoft Azure. Engagements are scoped and delivered remotely, with on-site work agreed per engagement.

Clouds

  • AWS

    Services
    Available
    ARIA
    Launching
  • Microsoft Azure

    Services
    Available
    ARIA
    Launching
  • Google Cloud

    Services
    Launching
    ARIA
    Launching

How we handle access, change and data

Today and next

What is real today, and what we are building

Every capability on this site carries its current state. We do not describe plans as delivered.

Available today

  • Cloud Security Assessment
  • Remediation & Hardening
  • Security Retainer
  • DevSecOps & CI/CD Security
  • Certification Technical Readiness
  • Secure Cloud Engineering
  • Resilience Review
  • Cost & Security Review

Being built

  • ARIALaunching
  • Google CloudLaunching
  • Penetration Testing (VAPT)Launching
  • Kubernetes SecurityLaunching

Where we are going

Services and software that reinforce each other

We are building Tricognita into a cloud security engineering company where expert security services and our own security software reinforce each other. Services solve complex security problems, the product automates the repeatable work, and together they let us serve more customers without relying entirely on growing human effort in step.

  1. 01

    Customer problems

  2. 02

    Engineering knowledge

  3. 03

    Repeatable workflows

  4. 04

    Automation in ARIA

Start with a scoping call.

Tell us about your cloud and what your customers or auditors are asking for. You receive a written scope before any work starts.