EterShieldDocs
etershield.com
PTLog in
Guide/Annexes

Annex C: Diagram style

Every diagram in the docs follows one style, the "EterShield Diagram": Apfel Grotezk, white nodes with a thin border, a single teal highlight. This page shows the four types and the rules.

Rules

  • About 12 nodes at most per diagram. Beyond that, split it in two.
  • Short labels, no trailing punctuation. Technical terms (Evidence, Gap, finding) stay as in the application.
  • Decisions with two exits are always labelled "Yes" and "No".
  • A single highlighted node, the one the reader must remember. Main arrows in teal.
  • Never emojis, not even inside diagrams. Never orange or shadows.
  • Every diagram has a short caption underneath.
  • Hierarchy trees are drawn with a shared trunk and no arrowheads.

Flowchart

For processes with decisions and deadlines. Start and end as pills, decisions as diamonds with "Yes" and "No" on the arrows, steps as rounded rectangles.

Yes

No

Incident detected

Log the incident

Is it significant?

Early warning to the CSIRT (24 h)

Incident notification (72 h)

Final report (1 month)

File with justification

Flow of a significant incident (NIS2, 24 h, 72 h and 1 month deadlines).

Sequence diagram

For exchanges between people and systems over time. Solid arrows for requests, dashed arrows for replies.

Authentication serverEterShieldUserEmail and passwordValidate credentialsAsk for a second factorAsk for the 2FA code6-digit codeValidate codeCode is validSigned in
Signing in with a second factor (2FA).

Hierarchy tree

For structure and dependency: modules, roles, frameworks. Groups in light grey, the root highlighted.

EterShield modules grouped by area.

State diagram

For the lifecycle of an object: policy, incident, finding. One state per box, the transition says what causes it.

approve

replaced by a newer version

Draft

Published

Archived

States of a policy: from draft to archived.
EterShield, an Eter Growth platform