PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Secure and Effective Logging in Golang: Best Practices and Tools

hackerone.com | blog | #secure-coding | #best-practices | #monitoring | #golang | #logging | #observability | #structured-logging
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

A guide to secure logging in Golang covering the standard log package, structured JSON logging with Apex/log and logrus, log level strategy, and why to avoid log.Fatal in production.
Published
Collected

Related coverage

blog · hackerone.com
Lessons Learned from Over a Decade of On-Call
HackerOne engineer Shubhi Gupta distills 12 years of on-call experience into guidance on designing alerts around what, when, who, and why—and how over-alerting erodes response quality.
blog · hackerone.com
The Top 5 Most Common Security Issues I Discover When Reviewing Code
A veteran code reviewer counts down the five security issues he finds most often, starting with PII and secrets leaking into logs and poor cryptography choices, with Python and Ruby examples.
blog · hackerone.com
The AWS Shared Responsibility Model: 3 Areas of Improvement to Make Today Part 3: Logging, Monitoring, and Alerting in AWS
Part 3 of the AWS shared responsibility series covers logging, monitoring, and alerting, explaining how CloudTrail, VPC Flow Logs, and CloudWatch combine to deliver high-value alerts to analysts.
blog · about.gitlab.com
How to build CI/CD observability at scale
CI/CD observability guide for self-managed GitLab: pairing gitlab-ci-pipelines-exporter with Prometheus and Grafana to track pipeline duration, job success rates, queue times, and runner utilization.
blog · semperis.com
AD Security 101: SIEM Tools and AD Monitoring
Why SIEMs alone can't secure AD monitoring: attackers bypass AD logs (DCShadow), and SIEMs face collection limits, configuration errors, processing gaps, stale threat intel, and false positives.
blog · hackerone.com
Golang's Improper Error Handling: A Subtle Path to Security Vulnerabilities
Golang's multi-value returns make unchecked errors a quiet security hazard: ignored failures can yield nil data or bypassed authentication. Best practice: always check errors and fail securely.
Back