Kirux · The NullGhost platform

Security with context.
Decisions with evidence.

Kirux is NullGhost’s platform for connecting security testing, operations and cloud posture to the findings you need to address.

One connected workflow
CloudIdentitiesEndpointsCode
KIRUXAnalysis and correlation
Findings in contextExecutive reports

From signal to evidence.

Reference architecture

How the assessment
connects.

A supporting platform: the team defines scope, the orchestrator coordinates tools against authorized assets and evidence is kept for review. Professional judgment remains part of the service.

DashboardScope and results
→
APIAssessment control
→
OrchestratorPhases + toolsOSINT → RECON → MAP → ATTACK → REPORT
→
Client assetsAuthorized scope only
AI modelLocal or API, configurable
EvidenceResults and findings
Cloud postureSteampipe + Powerpipe
Cloud accountAgreed permissions

Simplified reference architecture, not a guaranteed production topology. Coverage and integrations are agreed per project.

Initial modules

Four modules.
Each with its evidence.

What each module does and what its output looks like. Examples are illustrative, with fictional data; they are not client results.

01 / OFFENSIVE SECURITY

Pentesting with defined scope

Web and network testing, evidence and verification. Authorization controls bound the targets; deterministic phases complement the agent’s analysis.

  • Five main phases: OSINT, RECON, MAP, ATTACK and REPORT.
  • The authorized scope is recorded before acting and bounds the targets.
  • Every finding is verified with evidence before it is recorded.
Illustrative example
OSINTRECONMAPATTACKREPORT

Current phase: RECON · target within the authorized scope

$ openssl s_client -connect portal.empresa-ejemplo.example:443 -tls1
Protocol  : TLSv1
Cipher    : ECDHE-RSA-AES256-SHA
Verify return code: 0 (ok)
HIGHNG-04Outdated TLS protocolVerified
02 / OPERATIONS

Connected signals

AI-assisted triage, AWS GuardDuty and Microsoft 365 context, and finding tracking to help prioritize response.

  • Gathers the signal with its context before classifying it.
  • The classification is a suggestion: an analyst confirms.
  • Every finding stays tracked until it is closed.
Illustrative example
SignalContextAssisted triageTracking
SignalGuardDuty · Recon:EC2/PortProbeUnprotectedPort
Resourcei-0abc…example · security group with no port 22 open to the Internet
SuggestionProbable noise. An analyst confirms.
TrackingReview in 7 days
03 / CLOUD + FINOPS

Risk and resource usage

AWS security posture and optimization opportunities, with a category for AI resources such as SageMaker and accelerated compute.

  • Posture review with Steampipe and Powerpipe on an AWS account, with agreed permissions.
  • FinOps identifies opportunities; it does not guarantee savings.
  • The AI category locates resources such as SageMaker notebooks and accelerated compute.
Illustrative example
S3 bucket with public accessFAIL
IAM role with administrator permissionsFAIL
Unencrypted EBS volumesFAIL
Multi-region CloudTrailPASS
FinOps · AI

SageMaker notebook with no recent activity (example)

Opportunity to review
04 / AI CONTROL

Choose where processing happens

Choose a local model with Ollama or an external provider. We agree on the operating mode, data involved and integrations before work begins.

  • Local or external-provider mode, depending on the project.
  • The data involved is agreed before operating.
  • Results are kept for review and for preparing the report.
Illustrative example
Local modelOllama

Processing happens on agreed infrastructure.

External providerConfigurable API

The data involved and the provider are agreed.

Verification

Evidence before
the conclusion.

Kirux builds on what we learned operating an offensive security agent: coverage needs evidence per phase, and no finding is believed in the same pass that produced it.

Read the research: When the agent decides →

Sample report

Evidence,
beyond an alert.

Here is what your report looks like. Every finding includes its severity, status and supporting evidence.

Real severityCited evidenceVerified ✓
Kirux — example reportsample data
  • Executive Summary
  • Recon
  • Findings
  • Evidence
  • Cloud AWS
  • Remediation
2Critical
5High
8Medium
100%With evidence
FindingSeveritySourceEvidenceVerified
Leaked credentials (infostealer)CRITBreachesverified record✓
Outdated TLS protocolHIGHHandshakeTLS version✓
Exposed development subdomainMEDLive hostsstatus 200✓
SPF softfail instead of hardfailMEDDNSdig TXT✓
Excessive IAM privilegesHIGHAWSIAM policy✓

Capabilities depend on configuration and the contracted service; published research does not imply production features.

FinOps identifies opportunities; it does not guarantee savings or measure the full ROI of AI on its own.

NullGhost researches, builds and supports. Services define scope and deliverables. Kirux supports operations. Research shares what we learn and what we keep evaluating.

Explore research →

A demo with your scope in mind

We review objectives, integrations and processing mode with you.

Request a Kirux demo →