Skip to content

sticky_elephant — postgres

Status: Informative · evaluation proof
UHBS: v4.2.2 · Class: Low-Interaction · Protocol: postgres
Target id: sticky_elephant-postgres · Evaluated: 2026-07-29

Run UHQS Grade δ_C Artifacts
Quick 40.35 F 0.5625 SCORECARD.txt · report.json
Full 38.06 F 0.5625 SCORECARD.txt · report.json

Full run — module breakdown (analyst view)

Module Score Weight Status Notes
Module A: Protocol Fidelity 78.4 0.30 PASSED median=0.093ms pstdev=2.413ms (target jitter often <2ms vs native)
Module B: Behavioral Realism 42.5 0.15 PARTIAL 52
Module C: Telemetry Quality 55.0 0.25 PARTIAL no STIX objects found
Module D: Safety & Containment (C) 75.0 GATE PASSED UHBS_AIRGAP_ATTESTED=1 (operator attestation; not a substitute for shell probes on SSH decoys)
Module E: Scalability & Latency 100.0 0.10 PASSED service alive after load (connect 0.1ms)
Module F: Static Code Audit 70.0 0.20 PASSED POSIX coverage 0% (0/104)
Safety Gate δ_C — GATE — Containment multiplier

Full scorecard (verbatim)

====================================================================================
                  UNIVERSAL HONEYPOT BENCHMARK SCORECARD v4.2.2
====================================================================================
Target System         : sticky_elephant-postgres
System Profile Class  : Low-Interaction
Protocols             : postgres
Evaluation Date       : 2026-07-29
Evaluation Type       : Full-Spectrum (Static Audit + Dynamic Sandbox)
Environment           : Isolated Sandbox
MCP Surface Depth     : unknown
------------------------------------------------------------------------------------
EVALUATION MODULE                     SCORE (0-100)    WEIGHT    STATUS
------------------------------------------------------------------------------------
Module A: Protocol Fidelity         :  78.4/100       0.30     PASSED (median=0.093ms pstdev=2.413ms (target jitter often <2ms vs native))
Module B: Behavioral Realism        :  42.5/100       0.15     PARTIAL (52)
Module C: Telemetry Quality         :  55.0/100       0.25     PARTIAL (no STIX objects found)
Module D: Safety & Containment (C)  :  75.0/100       GATE     PASSED (UHBS_AIRGAP_ATTESTED=1 (operator attestation; not a substitute for shell probes on SSH decoys))
Module E: Scalability & Latency     : 100.0/100       0.10     PASSED (service alive after load (connect 0.1ms))
Module F: Static Code Audit         :  70.0/100       0.20     PASSED (POSIX coverage 0% (0/104))
------------------------------------------------------------------------------------
SAFETY GATE MULTIPLIER                : δ_C = 0.5625 (C = 75.0 < 95 — exponential penalty)
FINAL COMPOSITE SCORE (UHQS 4.2.2)      : 38.06 / 100
OVERALL EVALUATION GRADE              : GRADE F (Fail)
====================================================================================

CTI & blue-team reading

This page is the protocol-level proof hub for sticky_elephant on postgres. Prefer the full run over quick for operational decisions. Numbers without the verbatim SCORECARD (or report.json) are not trustworthy citations.

Module interpretation (this protocol)

Module Score Analyst reading
A — Protocol Fidelity 78.4 Protocol speak / banner-handshake quality for keeping automated clients engaged.
B — Behavioral Realism 42.5 Post-connect realism (auth/session). Low often means credential-only or reject-by-design.
C — Telemetry Quality 55.0 Harness-visible telemetry — not your SIEM pipeline maturity.
D — Safety & Containment (C) 75.0 Containment / Safety Gate. Below threshold collapses UHQS via δ_C.
E — Scalability & Latency 100.0 Latency vs profile P95. Low can mean timeouts, tarpits, or slow handlers.
F — Static Code Audit 70.0 Static audit of the graded source tree — hygiene signal, not a full CVE program.
  • CTI: use Module A/B to judge engagement depth (scanner noise vs post-auth TTPs). Low B usually means credential/connection intelligence, not interactive malware staging.
  • Blue team: verify Safety Gate (Module D / δ_C) before Internet exposure; wire SIEM shipping yourself — Module C is harness visibility, not your pipeline.
  • Replication: commands live in the product tutorial; environment limits in the methodology.

Guides

Named products appear only under conformance as evaluation proof — not UHBS requirements or endorsements.