Most of it is straightforward (a policy, an ITAM plan etc) but it also includes the need to define a risk framework which includes: This is a small set of requirements, but many people will not really know what it means, so I thought I’d explain for this month’s blog – but without going into
Software Recycling Process’ goal: To uninstall software with a view to reusing it at a later date; Software Removal Process’ goal: To uninstall software with a view to NEVER using this title ever again. The consequences of removing a software title from our IT estate cascades a series of activities that we wouldn’t adopt if we were
KF: Tell me who you are and what you do… and how did you get into cyber and where you are now? ND: I’m Nick Drage, and I’m currently a “cybersecurity strategist” of a sort, but spending time in game design as well. My career has been very unplanned, evolving through system and network administration
In response to the tensions and inconsistencies in the audit process, we have authored a draft Code of Conduct for Software Audits (“The Code”), which aims to capture and document reasonable market practice in software auditing, as currently no such document exists.