Added article on logging!

404salad · Mar 8, 2024 · e1b333c · e1b333c
1 parent 563e662
commit e1b333c
Show file tree

Hide file tree

Showing 4 changed files with 55 additions and 0 deletions.
diff --git a/cli/content/On Logging.md b/cli/content/On Logging.md
@@ -0,0 +1,10 @@
+> just log everything 
+
+Seems like a good idea. Storage is cheap, logs help debug, and they are useful in incident response, where all information you can get your hands on matters. But logs come with their downsides. Unprotected logs are a treasure trove of information to hackers and provide deep insight into how a system works.
+
+Everything from event logs, system logs, resource logs can and will be exploited if they fall into the wrong hands. This doesn't only involve external threat actors but internal threats like employees (whatever the reason might be). Logs should be treated like any other protected resource, and companies should follow proper access management protocols to safeguard themselves.
+
+There is a delicate balance between the amount of logs and their usefulness, and the amount has a point of diminishing returns. Proper alert systems should accompany logs to automate their usefulness. Each organization will have different needs and should adopt a standard logging system to ensure easy management.
+
+In summary, log what you need to but not needlessly as it increases the attack surface. 
+There is a cost to logs don't pay with security. 
diff --git a/cli/dist/articles/On Logging.html b/cli/dist/articles/On Logging.html
@@ -0,0 +1,25 @@
+
+<!DOCTYPE html>
+    <html lang="en">
+    <head>
+    <meta charset="UTF-8">
+
+    <link rel="stylesheet" href="../css/pico.lime.min.css">
+    <title>On Logging</title>
+</head>
+<body class="container">
+<a href='../index.html'>home</a>
+<br>
+<h1> | On Logging | </h1>
+<hr>
+<blockquote>
+<p>just log everything </p>
+</blockquote>
+<p>Seems like a good idea. Storage is cheap, logs help debug, and they are useful in incident response, where all information you can get your hands on matters. But logs come with their downsides. Unprotected logs are a treasure trove of information to hackers and provide deep insight into how a system works.</p>
+<p>Everything from event logs, system logs, resource logs can and will be exploited if they fall into the wrong hands. This doesn’t only involve external threat actors but internal threats like employees (whatever the reason might be). Logs should be treated like any other protected resource, and companies should follow proper access management protocols to safeguard themselves.</p>
+<p>There is a delicate balance between the amount of logs and their usefulness, and the amount has a point of diminishing returns. Proper alert systems should accompany logs to automate their usefulness. Each organization will have different needs and should adopt a standard logging system to ensure easy management.</p>
+<p>In summary, log what you need to but not needlessly as it increases the attack surface. 
+There is a cost to logs don’t pay with security. </p>
+
+</body>
+</html>
diff --git a/cli/dist/articles/on logging.html b/cli/dist/articles/on logging.html
@@ -0,0 +1,18 @@
+
+<!DOCTYPE html>
+    <html lang="en">
+    <head>
+    <meta charset="UTF-8">
+
+    <link rel="stylesheet" href="../css/pico.lime.min.css">
+    <title>on logging</title>
+</head>
+<body class="container">
+<a href='../index.html'>home</a>
+<br>
+<h1> | on logging | </h1>
+<hr>
+<p>Logging everything seems very useful </p>
+
+</body>
+</html>
diff --git a/cli/dist/index.html b/cli/dist/index.html
@@ -41,6 +41,8 @@ <h6>Sahil Upasane</h6>
                 <a href="articles/Cronjobs.html"> Cronjobs </a>
             </article><article>
                 <a href="articles/Every Programmer Should Watch  Conference Talks on YouTube.html"> Every Programmer Should Watch  Conference Talks on YouTube </a>
+            </article><article>
+                <a href="articles/On Logging.html"> On Logging </a>
             </article>
             </section>
         </body>