Out Of Control (Aalya) Mac OS
- On the Menu Bar, click the Apple menu then select System Preferences Click Security & Privacy. Click the Privacy tab. Click the Unlock icon in the bottom-left, then enter your Mac username and password.
- On Mac OS X, though, things are more complicated because the use of framework builds makes it common to encounter multiple instances of even the same major version of Python. I suggest you first understand and be comfortable with how to manage framework installs on Mac OS X.
- On a Mac with Apple silicon: Choose Apple menu Shut Down, press and hold the power button until you see “Loading startup options,” select Options, click Continue, then follow the onscreen instructions.
Open the Application Chooser by pressing VO-F1-F1 or, if you’re using VoiceOver gestures, double-tap near the left edge of the trackpad. Choose Finder in the Application Chooser. You can also use Mac OS X shortcuts by pressing Command-Tab and then using the arrow keys to navigate to the Finder. If a Finder window was open, you go to that window.
You can choose from icon, list, column, or Cover Flow view. In Cover Flow view, the browser is split horizontally into two sections. The top section is a graphical view of each item, such as folder icons or a preview of the first page of a document. The bottom section is a list view of the items.
To jump, press VO-J. If you’re using VoiceOver gestures, keep a finger on the trackpad and press the Control key.
Icon view: Use the arrow keys to move to the item you want.
List view: To move down the list rows, press VO-Down Arrow. To expand and collapse a folder, press VO-. To move the VoiceOver cursor across a row and hear information about an item, press VO-Right Arrow. Or press VO-R to hear the entire row read at once.
Column view: To move down the list until you find the folder or file you want, use the Down Arrow key. To move into subfolders, press the Right Arrow key.
Cover Flow view: To flip through the items in the top section and move automatically through the corresponding list rows in the bottom section, press the Left Arrow or Right Arrow key.
When you find the file or folder you want to open, use the Finder shortcut Command-O or Command-Down Arrow to open it.VoiceOver announces when you have selected an alias or a file or folder you don’t have permission to open.
-->Applies to:
Want to experience Microsoft Defender for Endpoint? Sign up for a free trial.
Important
Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Requirements
Device control for macOS has the following prerequisites:
Microsoft Defender for Endpoint entitlement (can be trial)
Minimum OS version: macOS 10.15.4 or higher
Minimum product version: 101.24.59
Your device must be running with system extensions (this is the default on macOS 11 Big Sur).
You can check if your device is running on system extensions by running the following command and verify that it is printing
endpoint_security_extension
to the console:Your device must be in
Beta
(previously calledInsiderFast
) Microsoft AutoUpdate update channel. For more information, see Deploy updates for Microsoft Defender for Endpoint on Mac.You can check the update channel using the following command:
If the above command does not print either
Beta
orInsiderFast
, execute the following command from the Terminal. The channel update takes effect next time the product starts (when the next product update is installed or when the device is rebooted).Alternatively, if you are in a managed environment (JAMF or Intune), you can configure the update channel remotely. For more information, see Deploy updates for Microsoft Defender for Endpoint on Mac.
Device control policy
To configure device control for macOS, you must create a policy that describes the restrictions you want to put in place within your organization.
The device control policy is included in the configuration profile used to configure all other product settings. For more information, see Configuration profile structure.
Within the configuration profile, the device control policy is defined in the following section:
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | deviceControl |
Data type | Dictionary (nested preference) |
Comments | See the following sections for a description of the dictionary contents. |
The device control policy can be used to:
Customize URL target for notifications raised by device control
When the device control policy that you have put in place is enforced on a device (for example, access to a removable media device is restricted), a notification is displayed to the user.
When end users click this notification, a web page is opened in the default browser. You can configure the URL that is opened when end users click the notification.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | navigationTarget |
Data type | String |
Comments | If not defined, the product uses a default URL pointing to a generic page explaining the action taken by the product. |
Allow or block removable devices
The removable media section of the device control policy is used to restrict access to removable media.
Note
The following types of removable media are currently supported and can be included in the policy: USB storage devices.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | removableMediaPolicy |
Data type | Dictionary (nested preference) |
Comments | See the following sections for a description of the dictionary contents. |
This section of the policy is hierarchical, allowing for maximum flexibility and covering a wide range of use cases. At the top level are vendors, identified by a vendor ID. For each vendor, there are products, identified by a product ID. Finally, for each product there are serial numbers denoting specific devices.
For information on how to find the device identifiers, see Look up device identifiers.
The policy is evaluated from the most specific entry to the most general one. Meaning, when a device is plugged in, the product tries to find the most specific match in the policy for each removable media device and apply the permissions at that level. If there is no match, then the next best match is applied, all the way to the permission specified at the top level, which is the default when a device does not match any other entry in the policy.
Policy enforcement level
Under the removable media section, there is an option to set the enforcement level, which can take one of the following values:
audit
- Under this enforcement level, if access to a device is restricted, a notification is displayed to the user, however the device can still be used. This enforcement level can be useful to evaluate the effectiveness of a policy.block
- Under this enforcement level, the operations that the user can perform on the device are limited to what is defined in the policy. Furthermore, a notification is raised to the user.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | enforcementLevel |
Data type | String |
Possible values | audit (default) block |
Default permission level
At the top level of the removable media section, you can configure the default permission level for devices that do not match anything else in the policy.
This setting can be set to:
none
- No operations can be performed on the device- A combination of the following values:
read
- Read operations are permitted on the devicewrite
- Write operations are permitted on the deviceexecute
- Execute operations are permitted on the device
Note
If none
is present in the permission level, any other permissions (read
, write
, or execute
) will be ignored.
Note
The execute
permission only refers to execution of Mach-O binaries. It does not include execution of scripts or other types of payloads.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | permission |
Data type | Array of strings |
Possible values | none read write execute |
Restrict removable media by vendor, product, and serial number
As described in Allow or block removable devices, removable media such as USB devices can be identified by the vendor ID, product ID, and serial number.
At the top level of the removable media policy, you can optionally define more granular restrictions at the vendor level.
The vendors
dictionary contains one or more entries, with each entry being identified by the vendor ID.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | vendors |
Data type | Dictionary (nested preference) |
For each vendor, you can specify the desired permission level for devices from that vendor.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | permission |
Data type | Array of strings |
Possible values | Same as Default permission level |
Furthermore, you can optionally specify the set of products belonging to that vendor for which more granular permissions are defined. The products
dictionary contains one or more entries, with each entry being identified by the product ID.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | products |
Data type | Dictionary (nested preference) |
For each product, you can specify the desired permission level for that product.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | permission |
Data type | Array of strings |
Possible values | Same as Default permission level |
Furthermore, you can specify an optional set of serial numbers for which more granular permissions are defined.
The serialNumbers
dictionary contains one or more entries, with each entry being identified by the serial number.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | serialNumbers |
Data type | Dictionary (nested preference) |
For each serial number, you can specify the desired permission level.
Section | Value |
---|---|
Domain | com.microsoft.wdav |
Key | permission |
Data type | Array of strings |
Possible values | Same as Default permission level |
Example device control policy
The following example shows how all of the above concepts can be combined into a device control policy. In the following example, note the hierarchical nature of the removable media policy.
We have included more examples of device control policies in the following documents:
Look up device identifiers
Mac Aaliyah Line
To find the vendor ID, product ID, and serial number of a USB device:
Log into a Mac device.
Plug in the USB device for which you want to look up the identifiers.
In the top-level menu of macOS, select About This Mac.
Select System Report.
From the left column, select USB.
Under USB Device Tree, navigate to the USB device that you plugged in.
The vendor ID, product ID, and serial number are displayed. When adding the vendor ID and product ID to the removable media policy, you must only add the part after
0x
. For example, in the below image, vendor ID is1000
and product ID is090c
.
Discover USB devices in your organization
You can view mount, unmount, and volume change events originating from USB devices in Microsoft Defender for Endpoint advanced hunting. These events can be helpful to identify suspicious usage activity or perform internal investigations.
Device control policy deployment
The device control policy must be included next to the other product settings, as described in Set preferences for Microsoft Defender for Endpoint on macOS.
This profile can be deployed using the instructions listed in Configuration profile deployment.
Troubleshooting tips
After pushing the configuration profile through Intune or JAMF, you can check if it was successfully picked up by the product by running the following command from the Terminal:
This command will print to standard output the device control policy that the product is using. In case this prints Policy is empty
, make sure that (a) the configuration profile has indeed been pushed to your device from the management console, and (b) it is a valid device control policy, as described in this document.
On a device where the policy has been delivered successfully and where there are one or more devices plugged in, you can run the following command to list all devices and the effective permissions applied to them.
Example of output:
In the above example, there is only one removable media device plugged in and it has read
and execute
permissions, according to the device control policy that was delivered to the device.