Chapter 4 — Academic writing

Lesson map

Lesson 04 published. Map, example, EX010.

flowchart TD
  N0["Learning outcomes"]
  N1["4.1 Explaining clearly"]
  N2["4.2 Citing correctly"]
  N3["4.3 Avoiding overclaiming"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX010"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["4.1 Explaining clearly"]
  N2["4.2 Citing correctly"]
  N3["4.3 Avoiding overclaiming"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX010"]

[Learning outcomes]
    |
    v
[4.1 Explaining clearly]
    |
    v
[4.2 Citing correctly]
    |
    v
[4.3 Avoiding overclaiming]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX010]

Learning outcomes

You will (1) write clear explanations of cryptographic ideas; (2) cite standards and textbooks correctly; (3) avoid overclaiming in security writing.

4.1 Explaining clearly

Priya's first essay explains to a general reader why passwords should not be stored in plain text. She uses a concrete example, a stolen database exposing every patron's password, then explains hashing with salts in plain words before introducing terms. Dr. Echeverría marks down a paragraph that used "hash", "salt" and "key derivation" without defining them. She learns to define each term once, use it consistently and prefer short sentences. Clear writing is not simplification; it is precision that readers can follow.

4.2 Citing correctly

For cryptographic claims Priya cites primary sources: FIPS 180-4 for SHA-256, RFC 9106 for Argon2, Katz and Lindell for definitions, and Menezes and colleagues' Handbook of Applied Cryptography for classical background. She cites the exact document and section where possible and checks that each link works. She avoids citing blog posts for facts that standards state, and never invents a reference or identifier. When a source is a draft, such as Boneh and Shoup's online textbook, she notes the version she read.

4.3 Avoiding overclaiming

Security writing often overclaims: "unbreakable", "completely secure" or "hackers cannot". Priya rewrites such phrases with precise claims: "Argon2id makes each password guess costly in time and memory, slowing offline guessing." She also states what the measure does not do: it does not protect weak passwords such as "library1" against determined guessing. Dr. Echeverría tells the class that careful limits make writing more persuasive to expert readers and protect authors when claims are tested. She keeps a list of banned phrases beside her desk as a reminder.

Worked example

Priya's essay defines terms once, cites FIPS 180-4 and RFC 9106, and replaces "unbreakable" with a precise claim and stated limit.

Synthetic case. The essay is invented; cited standards are real.

Errors and limits

Citations to secondary sources can carry errors; check the primary document. Precise language still needs a correct technical basis.

Exercises

• EX010 — Defining terms. What did Dr. Echeverría mark down, and why?
  Show marking criteria

  Rubric: 3 = terms like hash and salt used without definition;; 2 = undefined jargon;; 1 = style;; 0 = none.
• EX011 — Primary sources. Which primary sources did Priya cite for SHA-256 and Argon2?
  Show marking criteria

  Rubric: 3 = FIPS 180-4 and RFC 9106;; 2 = one;; 1 = blog;; 0 = none.
• EX012 — Precise rewrite. Rewrite "Argon2 makes passwords unbreakable" precisely.
  Show marking criteria

  Rubric: 3 = Argon2id makes each guess costly in time and memory, slowing offline guessing; weak passwords remain at risk;; 2 = partial;; 1 = unchanged;; 0 = none.

Synthesis

Good security writing defines terms, cites primary sources and states claims with their limits.

Continue studying — chapter 04 of 40

← Chapter 03 (draft) · Course chapter index · Chapter 05 (draft) →