01 / 08
Gi
Integrity / rectitude · pronounced gee
“Let your code be true and your actions provable.”
The virtue
Make your actions accountable.
Security depends on knowing who did what, and why.
Authentication establishes identity. Logging records action. Digital signatures establish authorship and integrity. Separation of duties prevents one person from controlling an entire process.
These controls matter because technical authority creates the ability to act without necessarily creating accountability.
The same applies to security decisions. If you approve an exception, accept a risk, disable a control or delay remediation, own the decision.
Security behaviour
Own your actions.
Non-repudiation and ethical conduct
Practices
- 1 / 4 · FoundationName the decision owner
- 2 / 4 · ControlledTime-bound exceptions
- 3 / 4 · MeasuredAudit attribution
- 4 / 4 · AdaptiveLearn from accountability failures
Controls
Interpretive readings — see the note on mappings above.
Full mapping, with notesFailure mode
Logs that can be edited by the people they incriminate.
When Gi is absent, decisions become difficult to trace. Exceptions become permanent. Privileged actions become anonymous. People optimise for immediate outcomes because nobody owns the consequences.
02 / 08
Yū
Courage · pronounced yoo
“Do not wait for the arrow. Go and find the archer.”
The virtue
Act when the evidence is incomplete.
An incident rarely announces itself with certainty.
A detection may be weak. A system may behave strangely. A user may report something that cannot yet be reproduced. Waiting for proof can give an attacker time.
Threat hunting exists because detection is incomplete. Incident response exists because waiting for perfect information is not an option.
Courage in security means investigating the uncomfortable possibility, escalating when the evidence warrants it and taking action before every question has been answered.
Security behaviour
Act under uncertainty.
Threat hunting and incident response
Practices
- 1 / 4 · FoundationDefine escalation thresholds
- 2 / 4 · ControlledExercise incident response
- 3 / 4 · MeasuredMeasure detection-to-investigation time
- 4 / 4 · AdaptiveTurn hunts into detections
Controls
Interpretive readings — see the note on mappings above.
Full mapping, with notesFailure mode
A SOC that only ever responds to alerts it configured itself.
When Yu is absent, teams wait for certainty. Analysts close unusual alerts because they cannot prove malicious activity. Architects avoid challenging projects. Incidents grow while everyone waits for someone else to act.
03 / 08
Jin
Benevolence · pronounced jin
“Wield the power to restrict as a duty to protect.”
The virtue
Protect the people who must use the control.
Security controls change how people work.
A control that creates constant friction will produce workarounds. Users will share credentials, bypass processes, create unmanaged solutions or ask for exceptions.
That behaviour is predictable. Design for it.
MFA, privileged access, endpoint restrictions, DLP and access controls must account for the legitimate work users need to perform.
The objective is to make the secure path usable enough that people can follow it.
Security behaviour
Design for the people using the control.
Usable security and human-centred design
Practices
- 1 / 4 · FoundationIdentify the user
- 2 / 4 · ControlledAutomate the safe path
- 3 / 4 · MeasuredMeasure abandonment
- 4 / 4 · AdaptiveRemove recurring friction
Controls
Interpretive readings — see the note on mappings above.
Full mapping, with notesFailure mode
Controls so hostile that the workaround becomes the real process.
When Jin is absent, security creates friction. Users work around controls. Engineers request permanent privileges. Developers move workloads to unmanaged platforms. Security becomes something people try to escape.
04 / 08
Rei
Respect · pronounced ray
“Grant only what duty demands. Surplus privilege invites disorder.”
The virtue
Respect every boundary you are given access to.
Privilege gives you capability. It does not give you permission to use that capability everywhere.
Least privilege limits access to what a role requires. Segmentation limits where systems can communicate. Data classification limits who should handle information. Separation of duties limits what one person can control.
The same principle applies to vulnerability disclosure. Finding a weakness does not make exploitation or public disclosure automatically appropriate.
Security depends on boundaries being meaningful.
Security behaviour
Respect boundaries.
Least privilege and access control
Practices
- 1 / 4 · FoundationDefine access requirements
- 2 / 4 · ControlledReview privileged access
- 3 / 4 · MeasuredTest access paths
- 4 / 4 · AdaptiveMove toward continuous authorisation
Controls
Interpretive readings — see the note on mappings above.
Full mapping, with notesFailure mode
Standing admin rights granted once and never reviewed.
When Rei is absent, access expands until capability becomes ownership. Administrators see everything. Networks communicate because they always have. Old accounts survive because nobody wants to disturb them.
05 / 08
Makoto
Sincerity · pronounced mah-koh-toh
“Report what is, not what is comfortable.”
The virtue
Make the system tell the truth.
Security decisions depend on the accuracy of the information behind them.
An inventory must represent the assets that actually exist. Logs must represent what actually happened. Configuration records must represent the deployed state. Integrity controls must detect unauthorised changes.
A dashboard showing 100% compliance is useless if the underlying inventory is incomplete.
A security control cannot compensate for false information upstream.
Security behaviour
Verify reality.
Data integrity and truthful reporting
Practices
- 1 / 4 · FoundationDefine authoritative sources
- 2 / 4 · ControlledReconcile inventories
- 3 / 4 · MeasuredMeasure inventory coverage
- 4 / 4 · AdaptiveAutomate reconciliation
Controls
Interpretive readings — see the note on mappings above.
Full mapping, with notesFailure mode
A dashboard tuned until it shows green.
When Makoto is absent, dashboards become fiction. Asset counts are wrong. "No alerts" means "no telemetry." Compliance percentages hide missing data.
06 / 08
Meiyo
Honour · pronounced may-yoh
“Your auditor is not watching. Do it correctly anyway.”
The virtue
Hold your standard when nobody is watching.
Compliance creates an external requirement. Security governance creates an internal responsibility.
Audits, certifications and regulatory obligations matter. They also create a temptation to optimise for evidence rather than behaviour.
The stronger test is what happens between audits.
Do you patch because the vulnerability is real? Do you review privileged access because the access creates risk? Do you investigate control failures when nobody has asked for the report?
Internal assurance exists to answer these questions.
Security behaviour
Maintain the standard without supervision.
Accountability, governance, audit
Practices
- 1 / 4 · FoundationDefine internal standards
- 2 / 4 · ControlledRun continuous assurance
- 3 / 4 · MeasuredMeasure control effectiveness
- 4 / 4 · AdaptiveRaise the internal standard
Controls
Interpretive readings — see the note on mappings above.
Full mapping, with notesFailure mode
Compliance theatre performed for the audit window.
When Meiyo is absent, the audit becomes the deadline. Teams fix what the auditor will inspect and defer everything else. Controls exist on paper while their operational state deteriorates.
07 / 08
Chūgi
Loyalty · pronounced choo-gee
“Guard the clan you belong to, and be worth guarding.”
The virtue
Protect what has been entrusted to you.
Every security role carries a form of stewardship.
An administrator receives privileged access. An engineer receives production access. A developer receives access to source code. An employee receives access to company information.
That access exists because someone trusts the role.
Security culture becomes effective when people understand that responsibility comes with access. Reporting a suspicious email, challenging an unsafe change or protecting a credential becomes part of doing the job correctly.
Technology can restrict behaviour. It cannot create responsibility.
Security behaviour
Treat access as responsibility.
Security culture and insider risk
Practices
- 1 / 4 · FoundationAssign system ownership
- 2 / 4 · ControlledInclude security in role definitions
- 3 / 4 · MeasuredMeasure ownership coverage
- 4 / 4 · AdaptivePush responsibility toward the edge
Controls
Interpretive readings — see the note on mappings above.
Full mapping, with notesFailure mode
Loyalty enforced by fear, which manufactures the insider it fears.
When Chugi is absent, security becomes someone else's job. Employees ignore suspicious activity. Administrators treat privileged access as personal capability. Teams assume another department owns the risk.
08 / 08
Jisei
Self-control · pronounced jee-say
“Every change deliberate. Every deployment reversible.”
The virtue
Control your actions before you control the system.
Most operational mistakes do not require malicious intent.
Someone changes a firewall rule under pressure. An administrator disables a control to solve an outage. An engineer modifies production without review. A temporary exception becomes permanent.
Change management, peer review, emergency procedures, rollback plans and privileged workflows exist because people make decisions under pressure.
Self-control is the behaviour. The process is how the organisation makes that behaviour repeatable.
The classical enumeration of Bushido is seven virtues: Gi, Yū, Jin, Rei, Makoto, Meiyo, and Chūgi. Self-control (自制 jisei, more commonly 克己 kokki) is a twentieth-century addition, largely downstream of Nitobe Inazō's 1900 book Bushido: The Soul of Japan, which framed samurai ethics for a Western readership. This site keeps eight because self-control maps to something real — change and configuration management — but it says so plainly rather than hiding the seam.
Security behaviour
Control your actions under pressure.
Change and configuration management
Practices
- 1 / 4 · FoundationDefine change classes
- 2 / 4 · ControlledUse just-in-time privilege
- 3 / 4 · MeasuredMeasure emergency changes
- 4 / 4 · AdaptiveReduce emergency demand
Controls
Interpretive readings — see the note on mappings above.
Full mapping, with notesFailure mode
The Friday hotfix nobody wrote down.
When Jisei is absent, operational pressure defeats security. Emergency changes become permanent. Temporary exclusions remain forever. Administrators accumulate privileges because removing them takes effort.
The pattern underneath
Read together, the eight virtues describe the behaviour that makes the technology work — one line each.
- 義Gi
- Own your actions.
- 勇Yū
- Act under uncertainty.
- 仁Jin
- Design for the people using the control.
- 礼Rei
- Respect boundaries.
- 誠Makoto
- Verify reality.
- 名誉Meiyo
- Maintain the standard without supervision.
- 忠義Chūgi
- Treat access as responsibility.
- 自制Jisei
- Control your actions under pressure.
Security controls define what an organisation can enforce. Character defines what people do when the control does not cover the situation.
If this holds
The pledge is a small, honest commitment device — a real signature over the text of this manifesto, not a badge.
Read the pledge