Describe Microsoft Secure Score benefits and capabilities-Describe security, compliance, privacy, and trust in Microsoft 365

Microsoft Secure Score is a feature found in the Microsoft 365 Defender portal that displays a dashboard of the network’s overall security posture, as shown in Figure 3-26. Secure Score is designed to help administrators learn more about the inner security workings of their networks.

FIGURE 3-26 The Microsoft Secure Score Overview dashboard

The Secure Score is a percentage found in the upper-left corner of the dashboard that reflects the number of points administrators achieve by performing security-related tasks and enacting items from the list of recommendations provided by Microsoft 365 Defender.

Directly beneath the Secure Score is a series of graphs that break down the score by specifying how many points were achieved in each of the four standard security categories: identity, data, device, and apps. Next to the graphs is the list of recommendations provided by Microsoft 365 Defender for each of the four categories and each licensed application.

For example, the first recommendation in the list calls for requiring multifactor authentication during administrative sign-ins. Double-clicking the recommendation switches the Microsoft Secure Score display to the Recommended Actions tab and opens a sidebar with more information, as shown in Figure 3-27.

FIGURE 3-27 A recommended action in the Microsoft Secure Score dashboard

This particular recommendation states that it is worth a possible nine points or 0.89 percent of the Secure Score value. As administrators complete the recommended task according to the instructions on the Implementation tab, Defender adds the points to the score and recalculates the Secure Score value.

Some tasks have binary solutions; an administrator either completes the task or does not and receives all or none of the points. In recommendations like this one, however, Defender awards partial points for partially completed tasks. It is also possible for the network to lose points and for its score to regress, such as when additional users who suffer from a security condition and are already recommended for remediation are added to the network.

Secure Score is not intended to be a set of instructions that administrators must follow by rote. Every enterprise network has its own needs and peculiarities, so there might be some recommendations that are not practical or possible in a specific situation.

For example, Defender might add the Block Win32 API calls from Office macros recommendation to a Secure Score page because it can help to prevent malicious code from being introduced into the network. However, if the network has users that require those API calls to do their jobs, then the administrators can create an exception like the one shown in Figure 3-28, indicating that they are willing to accept the risk or that they have some other means of preventing macro intrusions in place.

FIGURE 3-28 Creating an exception in the Microsoft Secure Score dashboard

Leave a Reply

Your email address will not be published. Required fields are marked *

Search

Popular Posts

  • Summary-Describe security, compliance, privacy, and trust in Microsoft 365
    Summary-Describe security, compliance, privacy, and trust in Microsoft 365

    Thought experiment In this thought experiment, demonstrate your skills and knowledge of the topics covered in this chapter. You can find the answers to this thought experiment in the next section. Ralph is the Director of the Brooklyn datacenter at Contoso Corp. The company currently has three office buildings in the New York area with…

  • Anticipating threats-Describe security, compliance, privacy, and trust in Microsoft 365
    Anticipating threats-Describe security, compliance, privacy, and trust in Microsoft 365

    Arguably, the most difficult part of the risk management planning process is trying to anticipate all the possible threats that could afflict the company’s data in the future. The three basic risk factors for the data—confidentiality, integrity, and availability—can be exploited in any number of specific ways, but the general threat categories are listed in…

  • Classifying users-Describe security, compliance, privacy, and trust in Microsoft 365
    Classifying users-Describe security, compliance, privacy, and trust in Microsoft 365

    The third element of the digital estate that must be considered when creating a risk management plan is the people who actually access the data. Whether deliberately or inadvertently, users are a constant vulnerability—if not an actual threat—to the organization’s data. After quantifying the organization’s information assets and their value and inventorying the hardware used…

Tags

There’s no content to show here yet.