Category filter

Configuration profile to restrict screen capturing on Mac

In today’s digital landscape, protecting sensitive information is crucial to prevent unauthorized access and distribution. Screen capturing allows unauthorized users to take snapshots or record videos of sensitive information, increasing the risk of data breaches. Admins can prevent users from capturing sensitive data and reduce the risk of data leakage by making use of a configuration profile to restrict screen capture, which makes it easier for them to manage various endpoints. This can be achieved by Hexnode’s Deploy Custom Configuration feature.

Disclaimer:

The sample configuration profiles provided below are created using various profile creator applications.

Note:

This configuration profile is supported on Mac devices running macOS 10.14.4 and above.

Configuration profile to disable screenshot and screen recording on Mac

<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> 
<plist version="1.0"> 
    <dict> 
        <key>PayloadContent</key> 
        <array>
            <dict> 
                <key>PayloadDescription</key> 
                <string>Configure restrictions</string> 
                <key>PayloadDisplayName</key> 
                <string>Restrictions</string> 
                <key>PayloadIdentifier</key> 
                <string>MacBook.81EEDFE3-CC0B-4D25-BA6D-90BF69C0176E</string> 
                <key>PayloadRemovalDisallowed</key> 
                <false/> 
                <key>PayloadType</key> 
                <string>com.apple.applicationaccess</string> 
                <key>PayloadUUID</key> 
                <string>551F3014-D042-4A87-AE03-E056667CB4FC</string> 
                <key>PayloadVersion</key> 
                <integer>1</integer> 
                <key>allowScreenShot</key> 
                <false/> 
            </dict> 
        </array> 
        <key>PayloadDescription</key> 
        <string>Disable the ability to create screenshots or screen recordings on macOS</string> 
        <key>PayloadDisplayName</key> 
        <string>Disable Screenshot Creation</string> 
        <key>PayloadIdentifier</key> 
        <string>MacBook.400C16DC-15A2-42E0-97C9-8CA79C810C6E</string> 
        <key>PayloadOrganization</key> 
        <string>Hexnode</string> 
        <key>PayloadScope</key> 
        <string>System</string> 
        <key>PayloadType</key> 
        <string>Configuration</string> 
        <key>PayloadUUID</key> 
        <string>400C16DC-15A2-42E0-97C9-8CA79C810C6E</string> 
        <key>PayloadVersion</key> 
        <integer>1</integer> 
    </dict>
</plist>

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>PayloadContent</key>

<array>

<dict>

<key>PayloadDescription</key>

<string>Configure restrictions</string>

<key>PayloadDisplayName</key>

<string>Restrictions</string>

<key>PayloadIdentifier</key>

<string>MacBook.81EEDFE3-CC0B-4D25-BA6D-90BF69C0176E</string>

<key>PayloadRemovalDisallowed</key>

<key>PayloadType</key>

<string>com.apple.applicationaccess</string>

<key>PayloadUUID</key>

<key>PayloadVersion</key>

<key>allowScreenShot</key>

</dict>

</array>

<key>PayloadDescription</key>

<string>Disable the ability to create screenshots or screen recordings on macOS</string>

<key>PayloadDisplayName</key>

<string>Disable Screenshot Creation</string>

<key>PayloadIdentifier</key>

<string>MacBook.400C16DC-15A2-42E0-97C9-8CA79C810C6E</string>

<key>PayloadOrganization</key>

<string>Hexnode</string>

<key>PayloadScope</key>

<string>System</string>

<key>PayloadType</key>

<string>Configuration</string>

<key>PayloadUUID</key>

<key>PayloadVersion</key>

</dict>

</plist>

In the above configuration profile, the <key>allowScreenShot</key> key should be set to false to disable the screenshot as well as the screen recording feature.

Notes:

To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
Ensure that you do not associate conflicting configurations with the devices.
Use wildcards to fetch key values from the portal.
It is recommended to manually validate the configuration profile on a system before executing it in bulk.
Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

Need more help?

Raise a Ticket

Ask Community

Chat With us