Security field guides — tools

The distinct tools record for Security field guides. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: field-guide:security-field-guides
Parent lifecycle: candidate
Page lane: tools
Lane lifecycle: proposed
Owner: Stan
Owner role: Not separately recorded
Owner status: Not separately recorded
Qualification result: NOT RUN · held for evidence and human review

Working browser surface: Field guides — documentation — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Authoritative tools lane tools and interfaces

Canonical tools-page assignments

Checksum Verifier (provider · required) — Use to compare a supplied checksum with a locally entered value or file reference when integrity evidence is available. Do not treat a matching checksum as proof of authenticity, secure storage, deployment, or current production state.
SHA-256 / Hash Function Demo (provider · required) — Use to demonstrate or record a SHA-256 digest for explicitly supplied text or locally referenced content. Do not use it as a signature, identity proof, malware verdict, or database authority.
Regex Tester (provider · optional) — Use to test bounded detection patterns against supplied sample strings, such as log formats or identifiers. Do not use it as a complete parser, sanitizer, authorization check, or proof that production traffic conforms.
CIDR / Subnet Calculator (provider · optional) — Use to inspect notation, address ranges, and subnet relationships in architecture notes or supplied network data. Do not infer reachable hosts, firewall state, ownership, routing, or live network connectivity.
HTTP Status Code / Header Lookup (provider · optional) — Use as a reference for interpreting supplied HTTP status codes or headers. Do not call endpoints or claim a web feature, provider connection, service health, or response from production.
Uptime / SLA Availability Calculator (provider · optional) — Use to calculate educational availability percentages from supplied durations or incident records. Do not present the result as a live SLA, customer-impact metric, or provider commitment.
Password / Passphrase Entropy Estimator (provider · optional) — Use only with synthetic examples or explicitly authorized non-secret samples to discuss estimated search space. Never request, store, or evaluate live credentials; do not call the estimate a security guarantee.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

Canonical tools-page assignments

checksum-verifierrequired · Record a deterministic comparison between supplied checksum evidence and a locally reviewed value.sha-256-hash-function-demorequired · Create or explain a SHA-256 digest for supplied, non-secret content while preserving provenance.regex-testeroptional · Test bounded security-related patterns against controlled sample text.cidr-subnet-calculatoroptional · Check CIDR notation and range arithmetic in architecture documentation.http-status-code-header-lookupoptional · Interpret supplied HTTP status and header terminology without making live-service claims.uptime-sla-availability-calculatoroptional · Compute availability from supplied time intervals for review-only reporting.password-passphrase-entropy-estimatoroptional · Demonstrate password-strength concepts with synthetic examples only.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

Hash equality can be mistaken for authenticity or safe custody.
Secret material may be entered into an inappropriate estimator or note.
Regex matches can create false confidence and may omit adversarial or malformed inputs.
CIDR arithmetic does not establish live reachability, routing, firewall configuration, or asset ownership.
HTTP status references do not establish that an endpoint was contacted or is healthy.
Availability calculations can be misleading when incident intervals or measurement scope are incomplete.
A local approval receipt is not a production authorization or external send.
Prototype and indexed routes are not evidence of connected web behavior.
Sensitive records may be exposed if visibility, attachments, or handoff recipients are not reviewed.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

source_record:field-guide:security-field-guides
agents/index.html#stan
field-guide:security-field-guides