Enterprise Library Test Guide - Willy .Net

Testing for Security Best Practices 133
Threat 1
Countermeasures
STRIDE
classification
Risk
Mitigation
Investigative
notes
Logging Application Block assemblies are not strong named.
The Logging Application Block assemblies must be strong named in order
to prevent malicious users from tampering with them or replacing them.
Tampering can occur when the assemblies are distributed or when the application
that uses the Logging Application Block is installed. Replacing the
legal assemblies with other assemblies can occur after the application is
installed. The legal assemblies also can be overridden at run time.
In addition to being strong named, assemblies should be signed with
Authenticode. Strong naming ensures the integrity of the code and Authenticode
ensures its authenticity. For more information about Authenticode, see
Authenticode on MSDN.
Tampering, Information Disclosure, Denial of Service, Elevation of Privileges
High
No
None
Table 8 lists the DREAD rating for threat 1.
Table 8: Threat 1 DREAD Rating
D R E A D Total Rating
3 3 2 3 3 14 High
Table 9 lists details about threat 2.
Table 9: Logging Application Block Threat 2
Threat 2
Name
Entry points
Threat description
Countermeasures
STRIDE
classification
Risk
Mitigation
Investigative
notes
Attackers can alter the configuration files.
Tampering with configuration files
Configuration files
The configuration files are in plaintext. They contain information about trace
listeners, formatters, and filters. An attacker can alter this information and
also add custom handlers. These actions can change the behavior of the
application block and expose sensitive information.
The configuration files should be encrypted or else plaintext configuration
files should not be used. The application should use the Cryptography Application
Block in conjunction with the Logging Application Block to encrypt
the configuration file.
Tampering, Information Disclosure, Denial of Service
High
No
None