Chapter 9 — Web3, blockchain and cryptoasset security: tools and methods
Lesson map
Lesson 09 published. Map, example, EX033.
flowchart TD
N0["Learning outcomes"]
N1["9.1 Choosing tools"]
N2["9.2 A consistent method"]
N3["9.3 Interpreting results carefully"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX033"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["9.1 Choosing tools"]
N2["9.2 A consistent method"]
N3["9.3 Interpreting results carefully"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX033"]
[Learning outcomes]
|
v
[9.1 Choosing tools]
|
v
[9.2 A consistent method]
|
v
[9.3 Interpreting results carefully]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX033]
Learning outcomes
You will (1) choose appropriate tools for checks; (2) follow a consistent method; (3) interpret tool results carefully.
9.1 Choosing tools
Aiko's toolkit includes the ledger client's command-line interface for node status, her Python scripts for comparisons, a log viewer, a configuration scanner and the hardware wallet utility used by staff signers. She chooses widely used, maintained tools from trusted sources and records each tool's version. She avoids installing unknown utilities on servers. Tools can introduce risk themselves: a compromised utility on a signer's computer could misrepresent a transaction. Mr Kowal reviews her list and asks her to note which tools can change systems and which only read.
9.2 A consistent method
Aiko follows the same method for each check: confirm scope, collect data with a recorded tool and version, compare with the expected state, record differences, confirm important differences manually and report. A consistent method makes results comparable over time and lets others repeat them. She writes the method on one page and attaches it to her work log. Consistency also helps her notice when something changes, because the method itself stays the same and only the system's behaviour differs from one check to the next.
9.3 Interpreting results carefully
Tools produce results that need interpretation. When her configuration scanner flags an open port on node two, Aiko checks and finds it is the peer port, expected and limited to the other nodes. She records it as expected with the reason. Durieux and colleagues' 2020 study of contract analysis tools found frequent disagreement and many missed issues, which shows that tool output is a starting point, not a verdict. Careful interpretation prevents both ignoring real problems and chasing harmless ones that waste a technician's limited time.
Worked example
Aiko follows a one-page method for every check and records a flagged peer port on node two as expected after manual confirmation.
Synthetic case. The toolkit and results are synthetic; Durieux et al. (2020) is a real source.
Errors and limits
Treating tool output as a verdict leads to chasing harmless flags or ignoring missed issues.
Exercises
- EX033 — Tool risk. How can a tool itself introduce risk? Rubric: 3 = a compromised utility could misrepresent a transaction;; 2 = compromise;; 1 = cost;; 0 = none.
- EX034 — Method step. Name one step in Aiko's method. Rubric: 3 = confirm important differences manually;; 2 = collect data with recorded version;; 1 = skip scope;; 0 = none.
- EX035 — Flag outcome. What was the flagged port on node two? Rubric: 3 = the expected peer port;; 2 = peer port;; 1 = a breach;; 0 = none.
- EX036 — Study lesson. What does the tool study show? Rubric: 3 = tool output is a starting point, not a verdict;; 2 = tools miss issues;; 1 = tools are perfect;; 0 = none.
Synthesis
Trusted tools, a consistent method and careful interpretation make checks dependable.
Continue studying — chapter 09 of 18
← Chapter 08 (draft) · Course chapter index · Chapter 10 (draft) →