| Hostname | IP Address | Status | Assigned To | Last Scan | Actions |
|---|---|---|---|---|---|
| MONT-AP-002 | 164.231.187.39 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-BE-002 | 164.231.187.37 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-DB-002 | 164.231.187.38 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-DC-003 | 164.231.187.34 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-DP-001 | 164.231.187.44 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-MB-002 | 164.231.187.36 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-SW-89108 | 22.19.120.22 | 2026-03-04 | |||
Finding DetailsEvaluate-STIG 1.2510.0 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 12/17/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-SW-89134 | 22.19.120.21 | 2026-03-04 | |||
Finding DetailsEvaluate-STIG 1.2510.0 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 12/17/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-VSF-003 | 164.231.187.42 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-VSF-004 | 164.231.187.43 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-WS-92010 | 164.231.187.45 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
| MONT-WS-92040 | 164.231.187.72 | 2026-01-14 | |||
Finding DetailsEvaluate-STIG 1.2507.5 (Scan-NETFramework4_Checks) found this to be NOT APPLICABLE on 10/23/2025 ResultHash: 499D611575281956E8E80B6EFACA64CD0F81EBAD ~~~~~ No machine.config or *.exe.config files found using .NET remoting with TCP channel so this requirement is NA. Comments |
|||||
Check Text
If .NET remoting with TCP channel is not used, this check is Not Applicable. Check the machine.config and the [application executable name].exe.config configuration files. For 32-bit systems, the "machine.config" file is contained in the following folder. %SYSTEMROOT%\Microsoft.NET\Framework\v4.0.30319\Config For 64-bit systems, the "machine.config" file is contained in the following folder. %SYSTEMROOT%\Microsoft.NET\Framework64\v4.0.30319\Config. Microsoft specifies locating the application config file in the same folder as the application executable (.exe) file. However, the developer does have the capability to specify a different location when the application is compiled. Therefore, if the config file is not found in the application home folder, a search of the system is required. If the [application name].exe.config file is not found on the system, then only a check of the machine.config file is required. Sample machine/application config file: <application name=“remoteserver”> <service> <activated type=“sample.my.object, myobjects”/> </service> <channels> <channel ref=“tcp server” port=“6134”/> </channels> </application> <serverProviders> <provider ref="wsdl" /> <formatter ref="soap" typeFilterLevel="Full" /> <formatter ref="binary" typeFilterLevel="Full" /> </serverProviders> Microsoft provides three "channels" that are used for remoting connectivity. They are the HTTP, TCP, and IPC channels. The channel that is used is specified via the <channels> element in the config file. TCP channel example: <channel ref=“tcp” port=“6134” secure="true"/> The TCP channel provides encryption and message integrity when the "secure" flag is set to "true" as shown in the above example. If the "secure" flag is not set to "true" for the TCP channel, this is a finding.
Fix Text
If .NET remoting with TCP channel is not used, this fix is Not Applicable. Ensure encryption and message integrity are used for TCP remoting channels. TCP remoting connections are protected via the secure=true configuration parameter. <channels> <channel ref="tcp" secure="true" /> </channels> Include the secure="true" flag in the channel ref parameter of the machine.config and [application name].exe.config file if the [application name].exe.config file exists on the system.