Logging issues

In Brief

Logging is the recording of information into storage that details who performed what and when they did it (like an audit trail) This can also cover debug messages implemented during development as well as any messages reflecting problems or states within the application. It should be an audit of everything that the business deems important to track about the applications use. Logging provides a detective method to ensure that the other security mechanisms being used are performing correctly.

Logging should be at least done at the following events:

Authentication: Successful & unsuccessful attempts.

Authorization requests.

Data manipulation: Any (CUD) Create, Update, Delete actions performed on the application.

Session activity: Termination/Logout events.

A good logging strategy should include the recording of any errors that occur in the application.
The application should have the ability to detect and record possible malicious use such as events that cause unexpected errors or defy the state model of the application. Users who attempt to get access to data that they shouldn’t (authorization), and incoming data that does not meet validation rules or has been tampered with. In general any error condition which could not occur without an attempt by the user to circumvent the application logic.

Logging should give us the information required to form a proper audit trail of a users actions.
Leading from this the date/time the actions were performed would be useful.
Logging functionality should not log a any personal or sensitive data pertaining to the user of function at hand that is being recorded; An example of this if your application is accepting HTTP GET the payload is in the URL and the GET shall be loged. This may result in logging sensitive data.

Logging should follow best practice regarding data validation; maximum length of information, malicious characters….
We should ensure that logging functionality only log’s messages of a reasonable length and that this length is enforced.

In Tomcat(5.5), if no custom logger is defined (log4J) then everything is logged via Commons Logging and ultimately ends up in catalina.out.
catalina.out grows endlessly and does not recycle/rollover. Log4J provides “Rollover” functionality, which limits the size of the log. Log4J also gives the option to specify “appenders” which can redirect the log data to other destinations such as a port, syslog or even a database or JMS.

The parts of log4J which should be considered apart from the actual data being logged by the application are contained in the log4j.properties file:

Vulnerable patterns examples for Logging

.NET

The following are issues one may look out for or question the development team /deployment team.
Logging and auditing are detective methods of fraud prevention. Much overlooked in the industry, which enables attackers to continue to attack/commit fraud without being detected.

They cover Windows and .NET issues:
Check that:

Windows native log puts a timestamp on all log entries.

GMT is set as the default time.

The Windows operating system can be configured to use network timeservers.

By default the event log will show: Name of the computer that generated the event; The application in the source field of the viewer. Additional information such as request identifier,username,and destination should be included in the body of the error event.

No sensitive or business critical information is sent to the application logs.

Application logs are not located in the web root directory.

Log policy allows different levels of log severity.

Writing to the Event Log

In the course of reviewing .NET code ensure that calls the EventLog object do not provide any confidential information.