Information Security Stack Exchange is a question and answer site for information security professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Can anyone help me to understand which kind of action I should make to mitigate this issue, which emerged from Microsoft Surface Attack Analyzer? How I can tighten the ACL? Is there a standard procedure to do?

Service BFE is vulnerable to tampering by multiple non-administrator accounts.

The service BFE is vulnerable to tampering by multiple non-administrator accounts.


Service: BFE
Registry keys writable by: 

Key: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\BFE\Parameters\Policy\Persistent\Callout

Account Rights
NT SERVICE\BFE (S-1-5-80-1383140227-27657646-1662666058-2710981023-2300958487)  KEY_SET_VALUE
Local Service (S-1-5-19)    WRITE_DAC


The relevant ACL(s) must be tightened.
share|improve this question

It says that this critical-for-security registry key is writeable by Local Service (S-1-5-19) WRITE_DAC, which is a key security risk. Its ACL should be changed to administrator level group or users using the security tab for this key in regedit. Alternatively, you could simply remove this WRITE, as you never know what kind of integrity feature it is. With one bad ACL you can compromise the complete OS.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.