<Application Built for Resillient Systems: Lessons from Catastrophic Events>
In an effort to be helpful, admist a catastrophic event, this app could help guide someone in the future. Ideal to heed the advice before such an event, but still useful for perhaps new businesses to understand during and after.
Simply plug in whatever the software or system issue maybe, as a bit of a guide:
Examples, Patch Mangement, QA, DDOS, Ransomeware, etc., then hit Play.
https://lnkd.in/gMC7asrX
Its just going to be par for the course, that we're all going to experience software issues. Its inevitable. Defects are part of the software world.
There are no Silver Bullets in Cybersecurity, and it only takes one defect or vulnerability to be exploited by an Attacker, to have issues.
Folks rushing to market, to develop software too fast, are bound to make mistakes. They are smart if they are catching defects while they are developing code. We need more of these solution providers.
In DevSecOps mentalities, "a blameless culture" refers to an environment where individuals are not blamed for failures or mistakes. Instead, the focus is on understanding and learning from incidents to improve processes and systems.
This approach encourages transparency, collaboration, and continuous improvement. By avoiding blame, teams can more openly discuss issues, leading to better problem solving and innovation.
This culture is essential for fostering trust and enabling rapid experimentation and iteration, which are key components of SuccessfulDevSecOps practices.
I'm wondering if we humans can borrow this approach that is similar, as we respond to all the future attacks, breaches, and catastophes too.
Emotions and angers are inevitable to surface in our future, but how we react to them is up to us. Can we be mindful and present?
We have to pass our wisdom, ambitions, and coping skills to future generations in Crisis.
Here's what I liked about the Cybersecurity Community that impressed me so.
1. Many came forward with a FAST WORKAROUND, showing team spirit
2. Many pointed to root ISSUES OF CONCERN like Quality Assurance Testing.
3. Many simply created AWARENESS to the Issue and acted like an informant
4. Some came to be DEFENDANTS and asked for grace in the ecosystem
5. Some debated without being rude or threatening, which allowed better opportunities for hearing the LEARNINGS thru the anger.
6. Some gave INSIGHTS ON WHAT TO EXPECT NEXT
7. Some emphasized the basics of SHIFTING LEFT , which is ideally for companies to catch issues early on in Development, as you are writing code.
8. Some cite a HOLISTIC approach, looking across the lifecycle of software.
Many social medialites, showed Partnership in the Ecosystem to help aid, some resorted to anger, and lost their sense of empathy.
We're all being tested!
#Bettertogether
Human Resources Leader
3moSo exciting! Congrats, Emily!