Skip to content

Update README.md #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,8 @@
The home of the OWASP Secure Logging Benchmark project which can be found
at: [www-project-secure-logging-benchmark](https://owasp.org/www-project-secure-logging-benchmark/).

Logging and monitoring is often an afterthought, or something that is built by developer for developers. This project
moved the mindset of the Developer from measuring system and preformance metrics or debugging towards logging
holistically. This project is a movement more than it is a standard. Logs give insights into code quality and bad logs
can be a symptom of bad code. This project contains training material and approached to move your logs to build in
security and forensics capabillities within the development cycle. This project will cover a varienty of things to
consider within designing the logging that is best for your application. It includes a Benchmarking tool which is still
in development to rate your logs in terms of maturity in terms of system monitoring, performance metrics, forensic
Logging and monitoring is often an afterthought, or something that is built by developers for developers. This project
moved the mindset of the developer from measuring system and performance metrics or debugging towards holistic logging. This project is a movement more than it is a standard. Logs give insights into code quality, and bad logs can be a symptom of bad code. This project contains training material and approaches to move your logs to build in
security and forensics capabilities within the development cycle. This project will cover a variety of considerations in designing the logging that is best for your application. It includes a benchmarking tool, which is still in development, to rate the maturity of your logs, in terms of system monitoring, performance metrics, forensic
information and even deductables for sensitive data disclosure. The aim is to empower developers to better develop logs
with future breaches in mind. This is not a silver bullet, but a tool to guiding how you think and approach logs.
with future breaches in mind. This is not a silver bullet, but a tool to guide how you think and approach logs.