<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security Monitoring on Pratik’s Localhost</title><link>https://pratikdabhi.in/tags/security-monitoring/</link><description>Recent content in Security Monitoring on Pratik’s Localhost</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>pratik.dabhi.4u@gmail.com (Pratik)</managingEditor><webMaster>pratik.dabhi.4u@gmail.com (Pratik)</webMaster><lastBuildDate>Sun, 13 Sep 2026 17:00:00 +0530</lastBuildDate><atom:link href="https://pratikdabhi.in/tags/security-monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>Protecting GitLab as a Crown Jewel: Security Logs, Dashboards, and Alerts with Wazuh</title><link>https://pratikdabhi.in/posts/gitlab-authentication-wazuh/</link><pubDate>Sun, 13 Sep 2026 17:00:00 +0530</pubDate><author>pratik.dabhi.4u@gmail.com (Pratik)</author><guid>https://pratikdabhi.in/posts/gitlab-authentication-wazuh/</guid><description>&lt;p&gt;For an organization that builds software, GitLab can be one of its crown jewels. It may hold proprietary source code, internal architecture, deployment configuration, and customer information in issues, attachments, or repository files. Depending on permissions and how delivery is configured, access to GitLab can also provide a way to change what the organization builds and deploys.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://pratikdabhi.in/posts/gitlab-authentication-wazuh/featured.png"/></item></channel></rss>