Building Microservices with Go

Logging

If we have protected our passwords and implemented decent security, we still need to know when we are under threat. In the previous chapter, we introduced logging, and logging can be a useful tool as part of your security policy. Consider someone attempting to brute force your application login; tracking high levels of authentication errors along with the source IP can be useful when you need to react to this threat. The IP address of the attacker can be blocked by the firewall.

The content of log files needs to consider the following attributes:

• Who is performing the action
• What has failed or succeeded
• When is the action occurring
• Why this has failed or succeeded
• How you can deal with the issue

The following example contains nowhere ...