Hi Community,
We’re reviewing a client’s SOPHOS policy configuration and noticed the following parameter is set:
1) My first question is on "endpoint.peripheral-control.enabled": true
From what we understand, this parameter determines whether the Peripheral Control feature is active. If it is set to false, then any other related settings — for example:
"endpoint.peripheral-control.actions.usb-storage": "blocked"
— would have no effect, and USB storage devices would still remain accessible.
Could someone please confirm whether this understanding is correct? Specifically, does setting enabled
to false
override all other peripheral control actions, regardless of their individual values?
2) My second question is related to the monitor
parameter within the same Peripheral Control policy:
"endpoint.peripheral-control.monitor": false
From what I understand, when this is set to false, the configured actions like block, allow, or read-only for devices are actively enforced.
However, when it is set to true, I’d like to confirm the exact behavior. Does enabling monitor mode mean:
The policy operates in a monitor-only state, where device activity is logged but not restricted, allowing users to connect and use USBs or other peripherals without enforcement?
Or
Do restrictions like block or read-only still apply, but the system just additionally logs the activity?
In short, when monitor
is set to true, do all peripherals behave as if no restrictions exist, or is it more of a dual-mode — monitor plus enforcement?
Would appreciate some clarity on this. Thanks again!
Thanks in advance!
Hello, Suhas Khade,
Thank you for reaching out to the Sophos Community Forum.
I appreciate your questions about the Sophos Peripheral Control policy settings. Here’s a clear explanation of how these parameters work if that helps you:
1. endpoint.peripheral-control.enabled
When set to false:
When set to true:
2. endpoint.peripheral-control.monitor
When set to false:
When set to true:
Key Points:
Setting enabled
to false
turns off all peripheral control, overriding any other settings.
Setting monitor
to true
activates a log-only mode: no restrictions are enforced, but device usage is recorded.
Please refer to this article for reference:
Let me know if you need any further help.
thanks for above. my client has set endpoint.peripheral-control.enabled: True and endpoint.peripheral-control.monitor: False on all custom & base policy under that Peripheral Control feature. so I feel that with .enabled:True if we are already enforcing action as per configured rules (e.g. block or allow, etc) via then with .monitor: False we are asking same thing to do isn't it ? because there is no logging or auditing happening at all ?
Can we safely recommend setting .monitor
to true
alongside .enabled: true
to log all peripheral device activity without affecting the current enforcement behavior?
Or would setting .monitor: true
override enforcement and allow unrestricted access, defeating the purpose of .enabled
?
Hello Suhas Khade,
Thank you for your follow-up and for providing details on your client’s configuration.
Please refer to this information if that helps you.
Current Configuration
endpoint.peripheral-control.enabled: true
endpoint.peripheral-control.monitor: false
With this setup:
Peripheral Control is fully enabled, and all configured actions (block, allow, or read-only) are actively enforced.
Only enforcement actions (for example, a device being blocked) are logged. General device usage isn’t comprehensively audited.
About the .monitor Parameter:
Setting .monitor: false means enforcement is active and only enforcement-related events are logged.
Setting .monitor: true switches the policy to monitor-only mode. In this mode, no restrictions are enforced, all peripherals are allowed, regardless of any block or allow settings. However, all device activity is logged for auditing purposes.
Key Points:
Monitor mode (.monitor: true) disables enforcement and only logs activity.
You can't have both enforcement and full activity logging simultaneously.
For active enforcement, keep .monitor: false. For comprehensive logging without enforcement, set .monitor: true.
Recommendation:
If your goal is to enforce device restrictions, don’t enable monitor mode (.monitor: true), as this will override enforcement and allow unrestricted access to all peripherals. At this time, Sophos Peripheral Control does not offer a mode that simultaneously provides both full enforcement and comprehensive logging.
There is currently no built-in feature in Sophos Peripheral Control that allows strict enforcement and full device activity logging simultaneously. If this capability is important for your organization, you can contact your Sophos account manager or partner to request that a feature enhancement be submitted on your behalf.
Please let us know if you have any further questions or need additional assistance.
Thanks for the explanation!
For capturing the “general device usage” and gaining broader visibility into all peripheral activities, would it be advisable to complement SOPHOS peripheral control logs with additional monitoring solutions such as:
Sophos Live Query (XDR) for real-time endpoint insights
Native Windows Event Logging focused on USB device events
Sysmon configured with SIEM integration to enable detailed and granular endpoint activity tracking
Hello Suhas Khade,
Thank you for your question regarding peripheral activity monitoring and Sophos Live Query (XDR) use.
Peripheral Activity Monitoring with Sophos:
About Sophos Live Query (XDR):
Recommendations:
Contact Your Account Manager or Partner:
Additional Monitoring Options:
Sysmon with SIEM Integration: Deploy Sysmon for granular device event tracking and integrate with a SIEM for centralised analysis and alerting.
Please refer to these articles for reference: