Edward A. Neyhart

Step 4 of 7 · Worked examples

The record, written as Cucumbs packets

Cucumbs passes work around in one fixed shape, so a reader can always tell what's known from what's guessed. Here are five pieces of Edward's record in that shape.

Root: axiom IV Entropy is the natural drift; intelligence is the force that refines it. The pairing is this site's own reading.

The career lines are marked FACT. The site's own reading of each example is marked INFERRED, so you can tell the record from the commentary.

Five examples

An early warning, turned into a business decision

SOURCE → TARGET
Edward's record → you
TASK
Show how a technical signal became action across the business.
STATE
Equifax, Senior Director, Security Engineering, 11/2007 to 03/2011. A global environment of more than 15 countries and more than 100,000 endpoints.
OBSERVATIONS
  • FACTHe detected Crimea-linked activity before it was public news.
EVIDENCE
  • FACTBriefed leadership on the business risk.
  • FACTPut geo-fencing in place.
  • FACTCoordinated with law enforcement.
HYPOTHESES
  • INFERREDThe value was in timing and translation: the signal reached leadership as a business risk while there was still time to act on it.
UNCERTAINTIES
  • UNKNOWNThe exact dates and technical details aren't on the public record.
REQUEST
If the role needs someone who can explain a technical threat to leadership in business terms, ask him about it.
RETURN
A conversation on LinkedIn.

The incident-to-detection loop

SOURCE → TARGET
Edward's record → you
TASK
Show what happens after an incident is closed.
STATE
SecurIT360, Senior Security Analyst and XDR/EDR subject matter expert, 03/2022 to 01/2024. Senior escalation point and 24/7 on-call for the SOC's major incidents.
OBSERVATIONS
  • FACTMore than 300 malware, ransomware, DDoS and breach incidents a year.
  • FACT60 to 90 minute average containment.
EVIDENCE
  • FACTRoot cause went back into tuned detections, playbooks and after-action reports.
  • FACTFalse positives fell by about 35%.
HYPOTHESES
  • INFERREDClosing the ticket wasn't the finish line. Each incident made the next detection better.
UNCERTAINTIES
  • UNKNOWNClient names and incident details stay private.
REQUEST
Use this as the model for how he would run response and detection together.
RETURN
Questions on LinkedIn.

A data center move with zero downtime

SOURCE → TARGET
Edward's record → you
TASK
Show a migration owned from bake-off to cutover.
STATE
Sprint, Security Engineer III, 11/2002 to 06/2004. A managed security platform serving more than 250 customers around the clock.
OBSERVATIONS
  • FACTHe selected the platform through a vendor bake-off and deployed Check Point Provider-1.
EVIDENCE
  • FACTThe cutover had zero downtime.
  • FACTHe then supported the customers as senior engineer and account manager, and stayed the senior escalation point.
HYPOTHESES
  • INFERREDOwning the work past the cutover is the same habit he still brings to every project.
UNCERTAINTIES
  • UNKNOWNCustomer names aren't public.
REQUEST
Read this alongside the ownership arc on the How he works page.
RETURN
Follow up on LinkedIn.

Designing around the work, not only the cutover

SOURCE → TARGET
Edward's record → you
TASK
Show what was left behind after a migration.
STATE
Insight Global, consultant to AT&T for the State of Georgia, 07/2011 to 01/2013. Inter-agency state departments.
OBSERVATIONS
  • FACTHe led a LAN and WAN redesign and a firewall and router migration, including a Juniper SSL VPN cutover.
EVIDENCE
  • FACTHe wrote the statewide lifecycle management processes that operations teams used for later integrations.
HYPOTHESES
  • INFERREDThe longer-lasting result was the process, because it kept working after the project ended.
UNCERTAINTIES
  • UNKNOWNWhich agencies were involved isn't on the public record.
REQUEST
Consider this for roles that need a migration to stick.
RETURN
Ask on LinkedIn.

Drill: sort the evidence

Early in an incident, the hardest part is keeping track of what you actually know. Sort each statement into one of the six Cucumbs evidence categories. The scenario is made up for practice. It isn't from a real incident. The hub explains the six tags in more depth on its evidence page.

  • FACTConfirmed and checked against a reliable record.
  • OBSERVEDSeen directly in data or on a system, but not yet confirmed as the whole story.
  • REPORTEDSomeone told you. Useful, but secondhand.
  • INFERREDReasoned from other evidence. It could still be wrong.
  • HYPOTHESISA possible explanation that still has to be tested.
  • UNKNOWNA gap you know about and haven't closed yet.
  1. The EDR console shows PowerShell launched by a Word document on one laptop.

    Show the answer

    OBSERVED You saw it in the tool yourself. It's real data, but it isn't yet the whole story.

  2. A user tells the help desk she opened an invoice attachment around 9 a.m.

    Show the answer

    REPORTED This is secondhand. It's worth recording, and worth checking against the logs.

  3. Two analysts each checked the file hash against the vendor's threat intelligence and confirmed the match.

    Show the answer

    FACT It was checked independently against a reliable source, so it can be treated as confirmed.

  4. The same hash turned up on three more hosts, so it probably spread over a file share.

    Show the answer

    INFERRED The spread is a reasonable conclusion from the evidence, but nobody has seen the file share do it yet.

  5. This might be the same group behind last quarter's phishing wave.

    Show the answer

    HYPOTHESIS An idea to test, not a finding. Write it down, then try to prove or disprove it.

  6. Nobody has checked yet whether the backups were reached.

    Show the answer

    UNKNOWN A known gap. Name it so it gets closed instead of forgotten.

  7. The firewall log records an outbound connection from that laptop to an unfamiliar address at 02:14.

    Show the answer

    OBSERVED Direct data from a system. What the connection was for is still open.

  8. The vendor's account manager says the product would have blocked this.

    Show the answer

    REPORTED A claim from someone else, and one with an interest in the answer. Test it before relying on it.

  9. The attacker was after payroll data.

    Show the answer

    HYPOTHESIS Motive is a guess until the evidence supports it.

How this page was built

Sections

  • Five examples
  • Drill: sort the evidence

Sources

  • Edward's career record
  • The Cucumbs message shape and evidence categories
  • A made-up practice scenario for the drill, labeled as such

Interactive part

Evidence-sorting drill.

It runs in your browser, sends nothing and stores nothing. With JavaScript off, the page still shows everything.

Checks before review

Banned-term scan, inline-code scan, outside-link check, HTML parse, a local serve, and screenshots on desktop and mobile with JavaScript on and off.

The full build record