.NET default proxy settings must be reviewed and approved.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-225234 | APPNET0066 | SV-225234r1188289_rule | CCI-000366 | low |
| Description | ||||
| The .Net framework can be configured to utilize a different proxy or altogether bypass the default proxy settings in the client's browser. This may lead to the framework using a proxy that is not approved for use. If the proxy is malicious, this could lead to a loss of application integrity and confidentiality. | ||||
| STIG | Date | |||
| Microsoft DotNet Framework 4.0 Security Technical Implementation Guide | 2026-02-12 | |||
Details
Check Text (C-225234r1188289_chk)
Open Windows explorer and search for all "*.exe.config" and "machine.config" files.
The referenced file is in the WinSxS directory (original source component file used when the Windows component was installed).
If the files under WinSxS are read-only and cannot be modified, this is not a finding.
Search each file for the "defaultProxy" element.
<defaultProxy
enabled="true|false"
useDefaultCredentials="true|false"
<bypasslist> … </bypasslist>
<proxy> … </proxy>
<module> … </module>
/>
If the "defaultProxy" setting "enabled=false" or if the "bypasslist", "module", or "proxy" child elements have configuration entries and there are no documented approvals from the authorizing official (AO), this is a finding.
If the "defaultProxy" element is empty or if "useSystemDefault =True” then the framework is using default browser settings, this is not a finding.
Fix Text (F-26921r468018_fix)
Open Windows explorer and search for all "*.exe.config" and "machine.config" files.
Search each file for the "defaultProxy" element.
Clear the values contained in the "defaultProxy" element, and the "bypasslist", "module", and "proxy" child elements.
The IAO must provide documented approvals of any non-default proxy servers.