Time to audit your MDM setup? Heres how to get it right
www.computerworld.com
Audits are never fun whether youre talking about a tax audit, energy audit, or industry compliance audits. But theyre necessary. And when it comes to mobile device management (MDM) deployments, theyre extra important, because mobile devices are endpoints that can expose your company to the security dangers and risk letting corporate data leak out.Heres what to consider as you plan an MDM audit and what to include.What do you need to achieve with an MDM auditAuditing something as broad as your MDM environment with its mix of identity products, federated cloud services, MDM solutions themselves, policies and groups, app inventories and the devices themselves can get, well, complicated.This means your first step is to determine what an MDM audit should cover.If youre confident in auditing other aspects of your IT stack, or your entire stack is from one vendor say youre a fully Microsoft shop with a stack built around Entra and Azure, both of which you already have audit programs for then you might just need to focus on Intune and your mobile device policies and configurations.But if you mix and match cloud services from multiple companies and your MDM solution is from a different vendor than everything else, youll need to look at your MDM links to everything else (and possibly how all your other systems link to each other). Auditing systems individually wont give you a holistic understanding of how they work together.If your company is subject to various compliance regimes (such as GDPR or HIPAA, for example), some subjects might be defined for you. Either way, set the scope of the audit so it can capture the systems, policies, user groups, device types, apps, user experiences and even the backend tools used in your environment.As with any audit, standard procedures need to be considered. Ideally, these basic processes will follow the model of other audit procedures already in place. There will always be some variation different systems have different functions and require measuring different metrics. But there should be some connective thread that runs through how you capture audit data, process it, report your findings and list corrective steps that need to be taken based on the results. An MDM audit will obviously focus on different things than a server or network security audit, but all three should come from the same basic template.As you consider the scope of an audit and its processes, make notes of the specific questions you need to answer and the data points you need to answer them. If this is your first MDM audit, brainstorming areas of importance and looking to outside resources such as your MDM (and related service) vendor can help define exactly what you need to ask. Be sure to consider each idea carefully to see whether its really significant or simply mission creep.If youve performed MDM audits in the past, youll want to review whether they captured the relevant information or let things fall between the cracks. And even if past audits went well, remember the mobile landscape and threat environment changes quickly. So youll need to account for any major changes such as the recent proliferation of generative AI since your last audit and decide whether your previous scope needs to be adjusted.The logisticsmatterHow the audit is done from a logistical perspective also matters. Some can be carried out simply by examining and testing back-end systems and have no real or direct user-facing components. MDM audits might require some fieldwork, virtual or in-person, to gather accurate data. And if various teams or groups of employees or managers need to be consulted or might be impacted during the audit, youll want to establish that up front for both the audit team and anyone affected.Who is the auditor(s)?The next step is determining who will conduct the audit. With something as broad as MDM, which touches several different domains network access, app licensing, user and group management, device and procurement from multiple vendors, endpoint security, user experience, general and mobile-specific policy requirements and so on it can be difficult to establish exactly whos ultimately responsible.This means MDM audits are often best done by a team where various stakeholders are represented.Should you consider a pre-audit?In some cases, you might know going into the process that there are areas that are problematic. These could include policies youve been meaning to update; the criteria on which you authorize user access to resources; how you manage or group users and devices; and significant updates mobile OS and app versions, backend systems that you have yet to get around to doing.Dealing with these known issues before the full audit occurs can make the entire process easier and shorten your departmental to-do list.The items you want to captureEvery audit will vary based on your needs and environment. The following isnt an exhaustive list, but these areas should be part of any MDM audit:Logs: Application and system logs from the MDM itself, and logs involving MDM interactions with devices and other services.Policies: Auditing MDM policies include the policies themselves (are they appropriate to your environment, security and user needs) and whether or not they are enforced as intended. As MDM provides a wealth of policy configurations and restrictions, this will be one of the major focus areas for an audit and it should be done across every major device/user demographic across an organizationDevice and network security: Broadly speaking, you need to ensure that information being transferred between devices and your network is secure, visible and functions appropriately regardless of how devices are connecting (corporate Wi-Fi, home or public W-Fi and cellular) as well as device integrity/malware checking.Device and data controls: One crucial feature of any MDM system is the ability to separate work and personal apps, settings and content. Rules related to this functionality should be clearly established and tested as widely as possible across your device fleet and user community. This can include encryption at rest and in transit andprocedures for handling things such as remote lock and remote wipe.Device enrollment and lifecycle processes.Mobile OS and app updates: Make sure these are consistent throughout your fleet and environment.Suspicious activity monitoring and reaction: What counts as suspicious activity can vary greatly, as can the intended reactions.After the auditAfter youve completed the audit, take time to sift through the results. Its also good to have multiple sets of eyes and perspectives on the data; an audit should be more than just a list of boxes to check. Seeing which criteria have been met or unmet is critical, but the question ofwhythe results are what they are is equally important. If there are devices or apps that are out of compliance, youll need to know that and understand why if youre going to remedy the issues. Your ultimate report should include this background and potential challenges during remediation.Remember, an audit isnt just about seeing where you miss the mark. Sometimes youll discover areas where your organization beats expectations, shows improvement from an earlier audit or helps you see your baseline compared to your overall industry. If something works well, you want to understand why. It might be something you can incorporate more broadly throughout your organization.The last major step is to create an action or remediation plan. (This is especially important if youre in an industry subject to regulation such as financial services or healthcare.) What this plan will look like can vary significantly from company to company and even from audit to audit.The most important thing is that this plan be actionable. Each item should be specific, have metrics that allow you to ensure it is being addressed and have a timetable for resolution. The main reason for an audit in the first place is to identify issues and make serious improvements. Performing an audit and then letting the results sit in a drawer is nothing more than audit theater you go through the motions, but dont act on the results.
0 Comments
·0 Shares
·0 Views