Consider adding something on OSINT and "just because it is open / public, doesn't mean there are no issues" under the looking at content section.

Not just from the pov of actions relating to processing data that is "public".

Case in point, Capital One hacker and that many people in the community have taken down OSINT posts relating to this as the person in question clearly has mental health issues. More of an ethical issue, but an interesting case of potentially unexpected implications of your actions. https://edition.cnn.com/2019/07/29/business/capital-one-data-breach/index.html. https://twitter.com/rayredacted/status/1156014110623985666?s=12.

add something on security.txt and RFC 9116 to relevant modules

Update slides for new SIM3

remove section 5 from the operational module as this is covered in secure comms

Consider adding some small commentary on NIS Directives and impact to the legal modules