Copyright and Licence¶

The Operational Resilience Security Model (ORSM), including its original written framework material, models, assessment concepts, diagrams and supporting documentation, is the work of Stefan Garczynski unless otherwise stated.

Purpose¶

ORSM has been developed to encourage practical improvement in security architecture and operational resilience.

The intention is to make the framework accessible for review, education and practical application while preserving clear attribution and responsible reuse.

Current Licensing Position¶

ORSM is currently published as a Public Draft.

A final public-use licence will be identified before the framework is declared a stable public release.

Until a specific licence is explicitly stated on this page, publication of ORSM should not be interpreted as granting rights beyond those provided automatically under applicable copyright law.

Intended Future Licensing¶

The preferred licensing direction is a Creative Commons licence that permits broad reuse while preserving attribution to the original framework and author.

The specific licence will be confirmed separately before stable release.

Attribution¶

Where ORSM material is quoted, referenced or discussed, attribution should identify:

Operational Resilience Security Model (ORSM) — Stefan Garczynski

Where practical, references should also identify the ORSM version used.

For example:

Operational Resilience Security Model (ORSM) 2.1 — Stefan Garczynski

Modifications and Derivative Material¶

Where organisations adapt ORSM material before a final public licence is confirmed, those adaptations should be clearly distinguished from the original ORSM framework.

Modified material should not be presented in a manner that implies approval, endorsement or authorship by Stefan Garczynski unless such approval has been explicitly provided.

Third-Party Material¶

Names, trademarks, standards, frameworks and other third-party material referenced by ORSM remain the property of their respective owners.

Their inclusion does not transfer ownership and does not imply endorsement, sponsorship or affiliation.

Stable Release¶

A future stable release should clearly state:

the applicable licence;
the framework version;
the publication date;
attribution requirements; and
any specific conditions governing redistribution or adaptation.