Broad technology discovery
Active, passive, API and existing-tool discovery across networks, endpoints, servers, virtualization, cloud, applications, databases, identity and supported cyber-physical systems.
Platform
Understand the estate.
Act on evidence.
Yerokom is designed to connect what an enterprise has, how it behaves, what threatens it, what depends on it, and what changed—then carry that context into governed operations and independent verification.
Understand the estate
Discovery becomes intelligence only when evidence survives normalization.
Yerokom combines active discovery, passive signals, cloud and SaaS APIs, native management protocols and existing enterprise tools. Each fact can retain source, observation time, confidence and staleness so teams can distinguish what is known from what is assumed.
Canonical asset intelligence
Correlate hardware, OS, firmware, software, interfaces, configuration, ownership, lifecycle, management paths, vulnerabilities and telemetry into one asset model.
Provenance & confidence
Preserve where a fact came from, when it was observed, how reliable it is, and whether sources disagree instead of hiding uncertainty.
Topology & dependencies
Connect L2/L3 paths, application and database dependencies, communication relationships, identity links and business-service context.
Lifecycle intelligence
Bring support state, versions, firmware, warranties, software inventory, certificates and historical change into the operating record.
Unknown & unmanaged assets
Surface assets that do not fit a known inventory source, then progressively identify and profile them without treating detection as authorization.
Correlate before prioritizing
Security and observability share the same dependency graph.
A CVE, an availability event, a configuration drift and a degraded user journey can affect the same business service. Yerokom is designed to make that relationship first-class.
Security context
Risk with reachability and business impact.
Connect vulnerabilities, advisories, weak configuration, lifecycle state and privileges to network exposure, compensating controls, dependencies and service criticality.
- Vulnerability and advisory context
- Reachability and exposure
- Privilege and identity relationships
- Control coverage
- Lifecycle and configuration risk
- Evidence-backed prioritization
Observability
Telemetry that keeps the infrastructure context.
Correlate logs, metrics, events, relevant traces, flow data, network paths, synthetic results and recent changes with the assets and services they describe.
- Logs, metrics and events
- Flow and path intelligence
- Application and API experience
- DNS, TLS and network timing
- Telemetry freshness and gaps
- Recent-change correlation
Investigation
Pivot without rebuilding context.
Move between an asset, identity, IP address, service, vulnerability, event and change while preserving the underlying evidence and relationship trail.
- Entity-centric investigation
- Dependency impact
- Evidence and source traceability
- Cross-domain search
- Change history
- Stale-data visibility
Validated change
Execution is the middle of the workflow—not the end.
Yerokom separates discovery from permission to write. Supported changes move through prerequisites, policy, authorization, controlled execution, independent after-state verification and declared recovery behavior.
Pre-flight
Check target identity, health, dependencies, compatibility, maintenance constraints, current state and expected blast radius before action.
Authorize
Bind approval to the intended targets, action, artifact, scope, policy and validity window rather than granting a generic write path.
Execute
Use the strongest supported management path: customer-owned tooling, native APIs and protocols, Site Gateway, or Yerokom Endpoint where appropriate.
Verify
Collect after-state independently and compare it with the intended outcome rather than equating command success with change success.
Recover
Preserve rollback or recovery behavior as part of the change plan and make failed verification an explicit operational state.
Prove
Retain before state, authorization, execution output, after state, provenance and verification evidence for investigation and governance.
Operating lifecycle
One model from discovery through proof.
Platform experiences can be specialized for infrastructure, security, observability and change while sharing the same underlying asset, relationship and evidence model.
UnderstandDiscoverIdentifyProfileNormalizeCorrelateMap
AssessObserveUnderstandAssessDetectPrioritize
ChangeCompareSimulatePlanAuthorizeExecute
ProveVerifyRecoverProve
Deployment architecture
Use the right management path for the target.
Yerokom is agentless-first for servers and infrastructure. Remote endpoints can use existing UEM/RMM capability or Yerokom Endpoint when required. Cloud and SaaS remain API-driven, and the Site Gateway handles customer-side discovery, telemetry and supported operations.
Yerokom control planeIdentity · policy · asset graph · security context · observability · workflow · evidence
Site GatewaySNMPv3, SSH, WinRM/PSRP, NETCONF, RESTCONF, gNMI, APIs and other supported native paths.
Existing platformsUEM/RMM, EDR/XDR, vulnerability, SIEM/observability, ITSM and other authoritative customer tools.
Yerokom EndpointRemote and off-network endpoints when an adequate existing enterprise management path is absent.
Cloud & SaaS APIsProvider-native inventory, identity, telemetry and management interfaces where supported and authorized.
Private evaluation
Bring a real environment and a real operational problem.
Start with read-only discovery and priority integrations. Expand to supported management workflows only after scope, controls and authorization are explicit.