From e3370d7b6b1426c11de15ff704e99c41ae1d9e64 Mon Sep 17 00:00:00 2001 From: John Benninghoff Date: Sun, 5 Jul 2026 10:54:51 -0500 Subject: [PATCH 1/2] Update URLs --- _posts/2019-09-15-chaos-resilience-engineering.md | 2 +- _posts/2020-05-01-chaos-resilience-secure360.md | 2 +- resources.md | 8 ++++---- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/_posts/2019-09-15-chaos-resilience-engineering.md b/_posts/2019-09-15-chaos-resilience-engineering.md index 5307139..3392136 100644 --- a/_posts/2019-09-15-chaos-resilience-engineering.md +++ b/_posts/2019-09-15-chaos-resilience-engineering.md @@ -41,7 +41,7 @@ I'm giving a talk next Tuesday (9/24) at at the [September OWASP MSP Meeting](ht 1. Introduce variables that reflect real world events like servers that crash, hard drives that malfunction, network connections that are severed, etc. 1. Try to disprove the hypothesis by looking for a difference in steady state between the control group and the experimental group. - [Resilience Engineering Book](https://www.crcpress.com/Resilience-Engineering-Concepts-and-Precepts/Woods-Hollnagel/p/book/9780754649045) -- [Four Potentials of Resilience](https://erikhollnagel.com/ideas/resilience%20assessment%20grid.html) +- [Four Potentials of Resilience](https://web.archive.org/web/20260317162249/https://erikhollnagel.com/ideas/resilience%20assessment%20grid.html) - [Etsy Blameless Post-Mortem](https://codeascraft.com/2016/11/17/debriefing-facilitation-guide/) ## How to get started and join the movement diff --git a/_posts/2020-05-01-chaos-resilience-secure360.md b/_posts/2020-05-01-chaos-resilience-secure360.md index cfd4619..6a988c0 100644 --- a/_posts/2020-05-01-chaos-resilience-secure360.md +++ b/_posts/2020-05-01-chaos-resilience-secure360.md @@ -31,7 +31,7 @@ My story is told in three acts: My journey to find chaos engineering (ACT I), Ch - [Chaos Engineering: System Resiliency in Practice](http://shop.oreilly.com/product/0636920203957.do) (new book, 2020) - [Principles of Chaos Engineering](https://principlesofchaos.org) - [Resilience Engineering](https://www.crcpress.com/Resilience-Engineering-Concepts-and-Precepts/Woods-Hollnagel/p/book/9780754649045) Book -- [The Four Potentials of Resilience](https://erikhollnagel.com/ideas/resilience%20assessment%20grid.html) +- [The Four Potentials of Resilience](https://web.archive.org/web/20260317162249/https://erikhollnagel.com/ideas/resilience%20assessment%20grid.html) - [Etsy Blameless Post-Mortem](https://codeascraft.com/2016/11/17/debriefing-facilitation-guide/) ## ACT III: What I’ve learned so far diff --git a/resources.md b/resources.md index 0887114..7e4af1a 100644 --- a/resources.md +++ b/resources.md @@ -14,9 +14,9 @@ Recommended reading and other resources for safety risk management. ## Short essays -* [Resilience Engineering](https://erikhollnagel.com/ideas/resilience-engineering.html) - Erik Hollnagel's account of the origins of Resilience Engineering -* [Resilience Assessment Grid](https://erikhollnagel.com/ideas/resilience%20assessment%20grid.html) - recommended for the succinct description of the four potentials of resilient performance in the beginning of the essay: Respond, Monitor, Learn, Anticipate -* [The NO view of 'human error'](https://erikhollnagel.com/ideas/no-view-of-human-error.html) - argues that we should stop using 'human error' as an explanation for accidents/failures as it is not helpful +* [Resilience Engineering](https://web.archive.org/web/20260515100808/https://erikhollnagel.com/ideas/resilience-engineering.html) - Erik Hollnagel's account of the origins of Resilience Engineering +* [Resilience Assessment Grid](https://web.archive.org/web/20260317162249/https://erikhollnagel.com/ideas/resilience%20assessment%20grid.html) - recommended for the succinct description of the four potentials of resilient performance in the beginning of the essay: Respond, Monitor, Learn, Anticipate +* [The NO view of 'human error'](https://web.archive.org/web/20250118071633/https://erikhollnagel.com/ideas/no-view-of-human-error.html) - argues that we should stop using 'human error' as an explanation for accidents/failures as it is not helpful * [From the coalface: an essay on the early history of sociotechnical systems](https://eight2late.wordpress.com/2015/04/07/from-the-coalface-an-essay-on-the-early-history-of-sociotechnical-systems/) - a blog post on how the idea of sociotechnical systems came from the study of coal mining in Britain and the insight that the "*best work arrangements come out of seeking a match between technical and social elements of the modern day workplace*" ## Books @@ -35,7 +35,7 @@ Recommended reading and other resources for safety risk management. * Hollnagel, E., Wears, R. L., & Braithwaite, J. (2015). From Safety-I to Safety-II: a white paper, [PDF](https://www.england.nhs.uk/signuptosafety/wp-content/uploads/sites/16/2015/10/safety-1-safety-2-whte-papr.pdf) - an evolution of Hollnagel's concept of Resilience Engineering, making the case that safety should focus not just on accidents (when things go unexpectedly poorly), but the full range of outcomes * Hollnagel, E. (2014). [Is safety a subject for science?](https://doi.org/10.1016/j.ssci.2013.07.025), [PDF](https://www.academia.edu/22733547/Is_safety_a_subject_for_science) - an earlier paper by Hollnagel that introduces Safety-II by arguing that we can’t have a science based on the non-occurrence of events (accidents) * Dekker, S. W. A. (2017). [Rasmussen's legacy and the long arm of rational choice](https://www.sciencedirect.com/science/article/abs/pii/S0003687016300254?via%3Dihub), [PDF](https://sidneydekker.com/wp-content/uploads/2024/12/RasmussenLongArm.pdf) - the paper explores the moral aspects behind our tendency to blame people for causing accidents, and how blame can be harmful -* Repenning, N. P., & Sterman, J. D. (2001). [Nobody Ever Gets Credit for Fixing Problems that Never Happened: CREATING AND SUSTAINING PROCESS IMPROVEMENT](https://doi.org/10.2307/41166101), [PDF](http://scripts.mit.edu/~jsterman/docs/Repenning-2001-NobodyEverGetsCredit.pdf) - an analysis of a challenge that faces many risk programs: why process improvement programs fail and succeed +* Repenning, N. P., & Sterman, J. D. (2001). [Nobody Ever Gets Credit for Fixing Problems that Never Happened: CREATING AND SUSTAINING PROCESS IMPROVEMENT](https://doi.org/10.2307/41166101), [PDF](https://web.mit.edu/nelsonr/www/Repenning%3DSterman_CMR_su01_.pdf) - an analysis of a challenge that faces many risk programs: why process improvement programs fail and succeed * Rae, A., Provan, D., Aboelssaad, H., & Alexander, R. (2020). [A manifesto for Reality-based Safety Science](https://doi.org/10.1016/j.ssci.2020.104654), [PDF](https://www.researchgate.net/profile/Andrew_Rae/publication/339289702_A_manifesto_for_Reality-based_Safety_Science/links/5e755d6d4585157b9a4da1dc/A-manifesto-for-Reality-based-Safety-Science.pdf) - a call for development of theories that can be empirically tested and are useful to practitioners, including a list of commitments for future research * Provan, D. J., Woods, D. D., Dekker, S. W. A., & Rae, A. J. (2020). [Safety II professionals: How resilience engineering can transform safety practice](https://doi.org/10.1016/j.ress.2019.106740), [PDF](https://research-repository.griffith.edu.au/bitstream/handle/10072/389308/Provan268657-Published.pdf?sequence=5) - a proposal for changing safety programs to adopt principles of Safety-II (also applicable to information risk management) From f23a5bfd7d6e0f543d9a20990f2c367da8afd9cf Mon Sep 17 00:00:00 2001 From: John Benninghoff Date: Sun, 5 Jul 2026 10:55:49 -0500 Subject: [PATCH 2/2] bundle update --- Gemfile.lock | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Gemfile.lock b/Gemfile.lock index 7a5790d..365dd7a 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -19,7 +19,7 @@ GEM public_suffix (>= 2.0.2, < 8.0) afm (1.0.0) ast (2.4.3) - async (2.40.0) + async (2.41.0) console (~> 1.29) fiber-annotation io-event (~> 1.11) @@ -143,7 +143,7 @@ GEM http_parser.rb (0.8.1) i18n (1.15.2) concurrent-ruby (~> 1.0) - io-event (1.16.4) + io-event (1.17.0) jekyll (3.10.0) addressable (~> 2.4) colorator (~> 1.0) @@ -390,7 +390,7 @@ CHECKSUMS addressable (2.9.0) sha256=7fdf6ac3660f7f4e867a0838be3f6cf722ace541dd97767fa42bc6cfa980c7af afm (1.0.0) sha256=5bd4d6f6241e7014ef090985ec6f4c3e9745f6de0828ddd58bc1efdd138f4545 ast (2.4.3) sha256=954615157c1d6a382bc27d690d973195e79db7f55e9765ac7c481c60bdb4d383 - async (2.40.0) sha256=52c7cf92b7e12fec4054f721b2fc9df401940d65a076f7e771cd6af18947af66 + async (2.41.0) sha256=c721ff2185760e9014639776aa1387a28012055c25aa960ff46f8478ed34acc5 base64 (0.3.0) sha256=27337aeabad6ffae05c265c450490628ef3ebd4b67be58257393227588f5a97b benchmark (0.5.0) sha256=465df122341aedcb81a2a24b4d3bd19b6c67c1530713fd533f3ff034e419236c bigdecimal (3.3.1) sha256=eaa01e228be54c4f9f53bf3cc34fe3d5e845c31963e7fcc5bedb05a4e7d52218 @@ -430,7 +430,7 @@ CHECKSUMS html-proofer (5.2.1) sha256=fdd958a7cbf9c3255fb96fe7cfc4e611f64e2706e469488a3326309ad007d2fd http_parser.rb (0.8.1) sha256=9ae8df145b39aa5398b2f90090d651c67bd8e2ebfe4507c966579f641e11097a i18n (1.15.2) sha256=00f9eb62412fe593b2a65a97daa75300d37abb8f7202ec748e94b6d46a9dd1b5 - io-event (1.16.4) sha256=98b04e3a5e374fe0ce20f69956d435a3430335920544e3c1a492bdf37c4bf6d6 + io-event (1.17.0) sha256=665c8883c4b7066e8241427056ce43d4e01747ec3a61e4a7badfdc4a316bfb84 jekyll (3.10.0) sha256=c4213b761dc7dfe7d499eb742d0476a02d8503e440c2610e19774ee7f0db8d90 jekyll-avatar (0.8.0) sha256=ea736277c2de54a21300122096700517972a722d5c68ca83f8723b4999abfd4b jekyll-coffeescript (1.2.2) sha256=894e71c2071a834e76eb7e8044944440a0c81c2c7092532fed1503b13d331110