{"id":226,"date":"2021-03-17T08:04:11","date_gmt":"2021-03-17T08:04:11","guid":{"rendered":"https:\/\/iconit.co.nz\/?page_id=226"},"modified":"2021-04-03T20:48:12","modified_gmt":"2021-04-03T20:48:12","slug":"it-audit-security","status":"publish","type":"page","link":"https:\/\/iconit.co.nz\/index.php\/it-audit-security\/","title":{"rendered":"IT Audit – Security"},"content":{"rendered":"\n

This is a segment of any review or audit that is rising to the top of the \u2018must have\u2019 for your board, or your sanity. Any IT security review or audit needs to include a security check at a base level, finding out things like how often users are forced to change their passwords. It would also include how complex those passwords need to be, how your anti-virus (endpoint<\/em> protection<\/em><\/a>) software is configured and working, things like that.<\/p>\n\n\n\n

But then the curve rises to start reporting other security risks at a higher level. This might include a data discovery to find out where all your data actually is and how it is (or isn\u2019t) protected, or a network penetration test. These can be time-consuming but revealing processes.<\/p>\n\n\n\n

A classic security mistake some IT teams make is to create a new virtual server in Azure, Microsoft\u2019s cloud service, or in Amazon Web Services (AWS), and then forget to put any endpoint protection (\u2018anti-virus\u2019) on that server. A server in Azure or AWS is no different to a server on your premises; it must be protected. These sorts of issues are highlighted in the IT Audit – Security phase.<\/p>\n\n\n\n

Head back to the IT Review\/IT Audit page.<\/a><\/p>\n\n\n\n

\n
\n

<\/p>

    <\/ul><\/div>\n
    \n
    \n\n\n\n\n\n\n\n<\/div>\n