You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opened discussion with ED and operations managers at OIDF. Placeholder will be created in the 2025 budget for this.
Comments back from ED:
As a whitepaper it can be a paid project. Is there lead editor or editor in mind?
If the DADE CG wanted to create the whitepaper proposal, that would be the next step to help lock in the budget from the board.
For noting, the proposal could also be turned into a blog post to publish before or after the board decision to fund the paper. Since there are no imminent conferences before board meeting in January a blog post and social media could help to gather feedback and partner interest and direct them to the CG.
Thank you @iglazer. I am happy to author the white paper with help from DADE members. As a related body of work, I have a project to try to restore my own personal systems from zero (e.g. I have access to my emergency kit in my safe deposit box, can I actually recover access to everything of importance) that I'll execute in the next couple months. Additionally, I have started to do some documentation on my home network config, where credentials are stored, etc. that feeds directly into a future emergency kit. I expect that this will reveal some surprising challenges which can be highlighted in a whitepaper. I also expect that this can be used to drive some kind of templates for people to develop their own "in case of emergency/break glass" kit.
As a next step, I suggest we put together a one paragraph proposal for the white paper that can be presented to the board. As a follow on item, we can use this to write a blog post or other social media posts to gain partner interest.
As discussed on the first DADE meeting, develop educational materials related to DADE for cyber security awareness month in October 2025.
Discuss potential deliverables on the December 13, 2024 call.
The text was updated successfully, but these errors were encountered: