<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Cassandra Chibueze on Medium]]></title>
        <description><![CDATA[Stories by Cassandra Chibueze on Medium]]></description>
        <link>https://medium.com/@cassandrachibueze1?source=rss-1e1b0b889b0e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yACvqA2w7on76WUKNPceIA.jpeg</url>
            <title>Stories by Cassandra Chibueze on Medium</title>
            <link>https://medium.com/@cassandrachibueze1?source=rss-1e1b0b889b0e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:51:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cassandrachibueze1/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Home Lab Chronicles — Lab 2: Integrating Imperva DAM with Active Directory for External…]]></title>
            <link>https://medium.com/@cassandrachibueze1/home-lab-chronicles-lab-2-integrating-imperva-dam-with-active-directory-for-external-052f2ad52004?source=rss-1e1b0b889b0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/052f2ad52004</guid>
            <dc:creator><![CDATA[Cassandra Chibueze]]></dc:creator>
            <pubDate>Sat, 12 Jul 2025 10:30:21 GMT</pubDate>
            <atom:updated>2025-07-12T10:30:21.953Z</atom:updated>
            <content:encoded><![CDATA[<h3>Home Lab Chronicles — Lab 2: Integrating Imperva DAM with Active Directory for External Authentication.</h3><p><strong>Introduction:</strong></p><p>This lab marks the beginning of something new in my home lab journey, working with Imperva SecureSphere DAM, a tool organizations use to monitor and protect their databases.</p><p>Imperva helps track database activity, flag suspicious behavior, and enforce security policies. But for it to understand who is doing what, it needs to connect to an identity source like Active Directory. That is exactly what I will be doing here.</p><p>In Lab 1, I configured a Windows Server as a Domain Controller with AD and DNS. In this lab, I will show how that setup can be connected to Imperva so users from AD can log into the Imperva Web UI and be assigned roles, just like in real environments.</p><p>This is my first Imperva focused lab. Before jumping into alerts or policies, this step lays the foundation for identity integration and role-based access control within the tool.</p><h3>What Is Imperva SecureSphere DAM?</h3><p>Imperva SecureSphere DAM (Database Activity Monitoring) is an enterprise-grade security platform built to monitor, audit, and protect your databases in real time. In today’s data-driven environments especially those handling financial, healthcare, or government information every database transaction matters. Unauthorized access, privilege misuse, or even accidental misconfiguration can lead to massive data exposure or compliance failures.</p><p>SecureSphere DAM steps in as a critical layer of defense, sitting between your sensitive data and potential threats, both internal and external. It goes beyond just logging actions it applies security intelligence, identity context, and policy enforcement to database activity, helping organizations maintain data integrity and comply with industry regulations.</p><p>Although Imperva is often introduced as a security tool, its depth of visibility, tight access controls, and audit-ready capabilities make it a strategic asset for InfoSec, Compliance, and IT teams alike.</p><h3>Why It’s Important, Especially in Finance and Regulated Environments?</h3><ul><li><strong>Tracks all database activity</strong>: Every login, read, write, schema change, and privilege escalation is logged for visibility and traceability.</li><li><strong>Associates activity with real users</strong>: By integrating with <strong>Active Directory (AD)</strong> or <strong>LDAP</strong>, every database action is tied to a specific person not just a generic system account.</li><li><strong>Detects and stops threats in real time</strong>: Imperva can trigger alerts or block malicious behavior like <strong>SQL injections</strong>, <strong>access outside business hours</strong>, or <strong>massive data reads</strong>.</li><li><strong>Protects against insider threats</strong>: Most data breaches today involve misuse of privileged accounts. Imperva audits <strong>DBAs and admins</strong> too, including their use of tools like <strong>stored procedures</strong> and <strong>triggers</strong>.</li><li><strong>Provides audit-ready reports</strong>: For compliance frameworks like <strong>PCI DSS</strong>, <strong>SOX</strong>, <strong>HIPAA</strong>, <strong>GDPR</strong>, <strong>NIST 800–53</strong>, and others.</li><li><strong><em>And many more features!</em></strong></li></ul><h3>Technical Components of SecureSphere DAM</h3><ul><li><strong>Agents</strong>: Installed on database servers, capturing traffic and sending it to the gateway.</li><li><strong>Gateways</strong>: Process traffic from multiple agents, apply policies, detect violations.</li><li><strong>Management Server (MX)</strong>: Central brain of the system used for Web UI access, configurations, reporting, and external integrations like LDAP or SIEM.</li></ul><h3>Objective of This Lab</h3><p>In this lab, we will:</p><ul><li>Create a Local Imperva Admin User</li><li>Configure External Authentication (LDAP)</li><li>Configure Imperva to Use the LDAP Source</li><li>Create a User in Active Directory for SecureSphere Login</li><li>Create an Externally Authenticated User</li></ul><p>Easy Peezy, yall. Fr!😄</p><p>This gives us a taste of how <strong>external authentication</strong> works, and sets us up nicely for more integrations.</p><p><strong>Tools Used</strong></p><ul><li><strong>Imperva DAM</strong> (MX CLI, and Web UI)</li><li><strong>Windows Server 2019</strong> with AD and DNS from Lab 1</li><li><strong>Domain</strong>: caslab.local</li><li><strong>Domain Controller IP</strong>: 10.255.0.101</li><li><strong>MX IP</strong>: 10.255.0.98</li></ul><h3>Step-by-Step Guide</h3><h4>Step 1: Create a Local Imperva Admin User</h4><ol><li>Log in to Imperva using the default admin account</li><li>Navigate to: <strong>Admin &gt; User Management</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IB3RfrKu_sdKFX0s" /></figure><p>3. Click <strong>Create User</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5lGb3aCgGGmfQZw9" /></figure><ul><li>Username: yourname (e.g., jane admin)</li><li>Role: Administrator</li><li>Password: Something secure or lab-friendly</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*smNDfNJc2scL8llV" /></figure><p>4. Logout and log back in with your new user to confirm it works</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/0*jd24Gee0dKguAwdo" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/0*VfkD7APg1ZJ2EOCJ" /><figcaption><em>You get prompted to update your password immediate on ftl (first time login)</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IfgOIS7fNW8RLhy5" /><figcaption>Successful login</figcaption></figure><p><em>IT WORKS!</em></p><p>Bonus tip:</p><p>You can customize password policy under <strong>Admin &gt; System Settings &gt; Password Policy</strong></p><blockquote><strong>Note:<br></strong> If you’re unable to select SecureSphere as the authenticator when creating a user — and the password fields are greyed out — it likely means your system is currently configured for External Authentication only.</blockquote><blockquote>To fix this:</blockquote><blockquote>Go to Admin → Security and Authentication → Authentication &amp; Authorization Configuration</blockquote><blockquote>Change User Authentication from External Only to User Specific</blockquote><blockquote>Save the changes</blockquote><blockquote>This will allow you to create both local users (SecureSphere) and external users (LDAP/AD) in your lab. Once this is done, retry the user creation step.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bpd7ZjzXrM1NRy0z" /></figure><h4>Step 2: Configure External Authentication (LDAP)</h4><p>This connects Imperva to your Active Directory so domain users can log in.</p><ol><li>Go to: <strong>Admin &gt; System Definitions &gt; External Systems</strong></li><li>Click <strong>Create</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u6fjgH-ad0w1Pul9" /></figure><p>3. In the pop-up:</p><ul><li><strong>Name</strong>: WS2K19-DC</li><li><strong>Type</strong>: LDAP Authentication &amp; Authorization</li></ul><p>4. Click <strong>Create</strong></p><p>5. Now configure it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/0*hBxOZ92wjw9-jNS1" /></figure><ul><li>Expand WS2K19-DC</li><li>Set the following values based on your own active directory server.</li></ul><p>Primary Server: 10.255.0.101 <em>(your DC IP)</em></p><p>Access Mode: User Account</p><p>Account DN: CN=Administrator,CN=Users,DC=caslab,DC=local <em>(your AD service account)</em></p><p>Password: e.g. Impuser123* (labfriendly password)</p><p>Base Path for Users: DC=caslab,DC=local</p><blockquote><strong>If you’re unsure of the DN or base path, use AD Users and Computers → right-click on user → Properties &gt; Attribute Editor</strong></blockquote><blockquote><strong>Run this command in PowerShell to get the Distinguished Name for the Base Path</strong></blockquote><pre>(Get-ADDomain).DistinguishedName</pre><blockquote><strong>Run this command in PowerShell to get the Account DN (which includes the CN) of a user:</strong></blockquote><pre>Get-ADUser -Identity Administrator | Select-Object DistinguishedName</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/0*-UIYJL10eDx9hCbz" /></figure><p><strong>The final look of the configuration.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/0*pEtJ-YRmLDnDw2fO" /></figure><ul><li>Click <strong>Save</strong></li><li>Scroll to the bottom and click <strong>Test Connection<br></strong> You should get a success message!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/0*kLfd0YuiZsnd3jQT" /></figure><p>6. Enable the LDAP if you haven’t already.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*Lt-NbotauEPs8wrc" /></figure><blockquote><strong>Note: In this lab setup, before testing the LDAP connection, ensure that both your Imperva MX and Windows Server (AD) are properly networked. In my case, they needed to meet the following conditions:<br> — Be on the same virtual network adapter (e.g., VMnet8)<br> — Use the same NAT configuration<br> — Fall within the same subnet (e.g., 10.255.0.x)<br> — Be able to ping each other using their assigned IP addresses</strong></blockquote><blockquote><strong>Tip: You can test connectivity by opening Command Prompt in each VM and running:<br> ping &lt;other-machine-IP&gt;</strong></blockquote><blockquote><strong>Tip 2: To test LDAP port access (389), open Command Prompt on your Windows Server and run:</strong></blockquote><blockquote><strong>telnet &lt;Imperva-MX-IP&gt; 389</strong></blockquote><blockquote><strong>(If telnet is not installed, go to Control Panel → Programs → Turn Windows features on or off → Check “Telnet Client” → Click OK.)</strong></blockquote><blockquote><strong>This ensures that Imperva can communicate with the Domain Controller over port 389 (LDAP) for authentication.</strong></blockquote><h4>Step 3: Configure Imperva to Use the LDAP Source</h4><ol><li>Go to: <strong>Admin &gt; Security &amp; Authentication &gt; Authentication &amp; Authorization Configuration</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/0*QCZlQLZpRRX38Me5" /></figure><p>2. Set:</p><ul><li><strong>User Authentication</strong>: User Specific</li><li><strong>External Authentication System</strong>: WS2K19-DC</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/0*7TRgIug2jXsRxnKY" /></figure><p>3. Click <strong>Save</strong></p><p><strong>This activates the option to create domain-based users in the Web UI.</strong></p><blockquote><strong>Side Note:</strong></blockquote><blockquote>If you receive an error like this when you try to enable the LDAP:<br> <strong>“This external system is being used by SecureSphere Admin ‘Authentication &amp; Authorization Configuration’. Please remove from this location then try again,”<br></strong> it usually means the system is already referencing another authentication method — possibly from a previous AD setup. In my case it was the other AD at the top of this screenshot:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*oPehwmtVv1bvnifv" /><figcaption>I was not able to enable my new AD WS2K19 because the previous one was in use.</figcaption></figure><blockquote><strong>To fix this:<br></strong> — Go to: Admin → Security and Authentication → Authentication &amp; Authorization Configuration<br> — Change <strong>User Authentication</strong> to <strong>SecureSphere Only</strong>, then save.<br> — You can now go back and enable or modify the LDAP system without issue.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/0*aGyrWH4jzTxVPd_A" /><figcaption>I can save it now.</figcaption></figure><p><strong><em>⚠️ This may not occur in a fresh environment. It often happens when an AD or LDAP setup was previously in place.</em></strong></p><h4>Step 4: Create a User in Active Directory for SecureSphere Login</h4><p>To allow Imperva SecureSphere to authenticate against your Active Directory, we’ll create a user account in AD. In our case, we’re creating <strong>John Doe</strong>.</p><blockquote><strong>Note</strong>: While you <em>can</em> create this user via the GUI (Active Directory Users and Computers), we strongly recommend using PowerShell to avoid common issues with expired passwords or login failures.</blockquote><h4>Creating John Doe via PowerShell</h4><p>Open <strong>PowerShell as Administrator</strong> on your Domain Controller and run:</p><pre>New-ADUser -Name &quot;John Doe&quot; `<br>-SamAccountName &quot;johndoe&quot; `<br>-UserPrincipalName &quot;johndoe@caslab.local&quot; `<br>-AccountPassword (ConvertTo-SecureString &quot;YourLabPass123!&quot; -AsPlainText -Force) `<br>-Enabled $true `<br>-PasswordNeverExpires $true `<br>-Path &quot;OU=Security,OU=LagosOU,DC=caslab,DC=local&quot;</pre><p><em>Note: The </em><em>-Path value above reflects the custom OU structure I created in </em><a href="https://medium.com/@cassandrachibueze1/home-lab-chronicles-0d0bf80e5012"><em>Lab 1 of this Home Lab Series</em></a><em>. Yours may differ depending on how your Active Directory is set up.</em></p><p>To find your exact path:</p><ul><li>Open <strong>Active Directory Users and Computers (ADUC)</strong></li><li>Right-click the desired OU &gt; <strong>Properties</strong> &gt; Copy the <strong>Distinguished Name</strong></li></ul><p>This ensures the user is created exactly where you want them in AD.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/0*XRf9qKt9vX_c_0oe" /></figure><h4>Why PowerShell?</h4><ul><li>Sets the password immediately</li><li>Prevents forced password change at login</li><li>Ensures the user account is active</li><li>Gives you control over the OU placement</li></ul><h4>Step 5: Create an Externally Authenticated User</h4><p>Let’s add a user from AD who can log into Imperva.</p><ol><li>Go to <strong>Admin &gt; User Management</strong></li><li>Click <strong>Create User</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/0*sOgV-LojipVWTzfa" /></figure><p>3. Click <strong>User Lookup</strong></p><ul><li>Enter SAM account name (e.g., johndoe)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/345/0*rAx92qnYoo56dZ6N" /><figcaption>Imperva will fetch the user from AD</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/0*S6RWFRhhKCI4lzPT" /><figcaption>The User is in the AD</figcaption></figure><blockquote><strong>Note: This screenshot below highlights the accuracy and synchronization achieved through LDAP integration. When attempting to create a user with the wrong display name (“johndoe”) as seen in the screenshot below, Imperva automatically cross-checked against Active Directory and flagged the mismatch, prompting that the user must be named “John Doe.” This ensures that account mapping aligns strictly with AD identity records a great example of how directory-based authentication prevents user misconfiguration.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/0*NMk-3Lj5K2KcMlib" /></figure><p>4. Assign a role: Administrator</p><p>5. Click <strong>Create</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/212/0*Tug7MtZ6Z-0kpqh-" /></figure><p>6. Now test:</p><ul><li>Log out of Imperva</li><li>Log in using the AD credentials:</li><li>Username: johndoe</li><li>Password: ********</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/0*VdyHaUDCvDGuMOXs" /></figure><blockquote><strong>If login succeeds like mine, your integration is working!</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/0*24OqtJPHHQVH91AT" /></figure><blockquote><strong>Success! This final screenshot confirms that the Active Directory user “John Doe” successfully logged into the Imperva SecureSphere Web UI. The timestamp under “Last login” proves that the authentication flow, from AD integration to user creation is working as intended. This completes the identity integration setup.</strong></blockquote><h3>Why This Lab Matters</h3><p>This isn’t just about tinkering with random tools. It’s about simulating how real organizations secure their most sensitive assets.</p><p>Imperva SecureSphere is a premium enterprise solution, not something freely available to everyone. That’s why labs like this are valuable, especially for those who have access to it at work, in a training environment, or through a home lab like mine.</p><p>Here’s what this lab helps you understand:</p><ul><li><strong>How AD gives Imperva identity awareness</strong></li><li><strong>How Imperva brings visibility and control over database activity</strong></li><li><strong>How identity + activity logs = end-to-end accountability</strong></li></ul><p>In a future lab, we will begin integrating this setup with Wazuh to explore centralized logging and correlation.</p><h3>🔜 Up Next:</h3><p><strong>Home Lab Chronicles — Lab 3: Creating Action Sets in Imperva for Alerts and Log Forwarding<br></strong> We’ll create policies and action sets so that logs and alerts get routed to external systems like Wazuh.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=052f2ad52004" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Home Lab Chronicles — Lab 1: Setting Up Windows Server as an Active Directory Domain Controller.]]></title>
            <link>https://medium.com/@cassandrachibueze1/home-lab-chronicles-lab-1-setting-up-windows-server-as-an-active-directory-domain-controller-0d0bf80e5012?source=rss-1e1b0b889b0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d0bf80e5012</guid>
            <dc:creator><![CDATA[Cassandra Chibueze]]></dc:creator>
            <pubDate>Sun, 22 Jun 2025 22:53:39 GMT</pubDate>
            <atom:updated>2025-06-22T22:53:39.460Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Welcome to the first post in my <strong>Home Lab Chronicles</strong>, where I’m building and documenting real-world infrastructure and security integrations from scratch.<br> In this lab, I configured a Windows Server as an <strong>Active Directory (AD)</strong> Domain Controller with <strong>DNS</strong>, laying the foundation for deeper integrations with tools like <strong>Imperva DAM</strong> and <strong>Wazuh</strong>.</p><blockquote><strong>Goal: Turn my Windows Server into an Active Directory Domain Controller with DNS support.</strong></blockquote><h3>Tools Used</h3><ul><li><strong>VMware Workstation Pro</strong> — to create and run the virtual machine</li><li><strong>Windows Server 2019</strong> — installed on the VM for this Active Directory setup</li></ul><blockquote><em>This setup was done on a personal laptop. No cloud or advanced hardware needed, just a virtual machine and a Windows Server ISO.</em></blockquote><h3>⚙Lab Environment</h3><ul><li><strong>OS</strong>: Windows Server 2019</li><li><strong>Virtualization</strong>: VMware Workstation (NAT Network)</li><li><strong>Server IP</strong>: 10.255.0.101</li><li><strong>Default Gateway</strong>: 10.255.0.2</li><li><strong>DNS</strong>: Configured locally on the same server</li><li><strong>Role(s)</strong>: Active Directory Domain Services (AD DS), DNS Server</li></ul><h3>Steps I Followed</h3><h4>Step 1: Renamed the Server</h4><ol><li>Open <strong>Server Manager</strong></li><li>Click <strong>Local Server</strong> on the left</li><li>Click the computer name (e.g., WS2K19-DC)</li><li>In the window that opens:</li></ol><ul><li>Click <strong>Change</strong></li><li>Set a new name (e.g., DC01)</li><li>Restart the server when prompted</li></ul><h4>Step 2: Assigned a Static IP Address</h4><ol><li>Open <strong>Control Panel</strong> &gt; <strong>Network and Sharing Center</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/0*eXYspo1koeIskUmJ" /></figure><p>2. Click <strong>Change adapter settings</strong></p><p>3. Right-click <strong>Ethernet</strong> &gt; <strong>Properties</strong></p><p>4. Select <strong>Internet Protocol Version 4 (TCP/IPv4)</strong> &gt; <strong>Properties</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/0*-tYynW3RHQt3pTr_" /></figure><p>5. Choose <strong>Use the following IP address</strong> and set:</p><ul><li>IP address: 10.255.0.101(or something free in your range)</li><li>Subnet mask: 255.255.255.0</li><li>Default gateway: your router IP (e.g., <em>10.255.0.2</em>)</li></ul><blockquote><strong>How I got the default gateway IP:</strong><br> I opened <strong>“Virtual Network Editor”</strong> in VMware Workstation, selected the NAT network (<strong>VMnet8</strong>), and clicked <strong>“NAT Settings…”</strong>. The Gateway IP (e.g., 10.255.0.2) was listed there. That’s the IP the VM uses to route traffic outside.</blockquote><ul><li>Preferred DNS server: set to <strong>same as IP</strong> (e.g., 10.255.0.101) — this will make sense once DNS is installed</li></ul><h4>Step 3: Installed AD DS and DNS Server Roles</h4><ol><li>Open <strong>Server Manager</strong></li><li>Click <strong>Add roles and features</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/0*rzXI1IPVZSltlJJi" /></figure><p>3. Click <strong>Next</strong> until you get to <strong>Server Roles</strong></p><p>4. Check <strong>Active Directory Domain Services</strong></p><ul><li>It will auto-check <strong>DNS Server or check it manually.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/0*tHVySj12TOYPk5X7" /></figure><p>5. Click <strong>Next</strong> until <strong>Install</strong> is available</p><p>6. Click <strong>Install</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/0*FZ_0kabZH2fHNURx" /></figure><p>7. Wait for installation to complete (don’t restart yet)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/0*vHtT1AYVc-rdspGv" /></figure><h4>Step 4: Promoted to Domain Controller</h4><ol><li>Click <strong>Promote this server to a domain controller</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/0*PfGquD7E6_bfvjcI" /></figure><p>2. Choose <strong>Add a new forest</strong>, and for the <strong>Root domain name</strong>, type:</p><ul><li>I chose Caslab.local (choose any name you like)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/0*i6h6q729SCsLsoOo" /></figure><p>3. On the <strong>Domain Controller Options</strong> screen:</p><ul><li>Leave defaults checked: <strong>Domain Name System (DNS)</strong> and <strong>Global Catalog (GC)</strong></li><li>Set a <strong>DSRM password</strong> (Directory Services Restore Mode) — store it somewhere safe</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/0*0uqwNg_C71goLsVM" /></figure><p>4. Continue through the wizard and click <strong>Install</strong> at the end</p><p>5. Server will <strong>restart automatically</strong> after promotion</p><h4>Step 5: Verified AD and DNS Installation</h4><blockquote>After reboot:</blockquote><ol><li>Log in: Caslab\Administrator and your password</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*0HaYdJ7bi199A05I" /></figure><p>2. Open <strong>Server Manager</strong> &gt; Tools:</p><ul><li>You will see <strong>Active Directory Users and Computers</strong></li><li><strong>DNS</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/0*Ax8GaLdHXEkbijn_" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/0*6-YbOVvAaxf9_wK6" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/0*cQZ0Sb5c4ZUP7XZ3" /></figure><h4>Step 6: Configured Reverse Lookup Zone</h4><h3><em>Why Create a Reverse Lookup Zone in DNS?</em></h3><p><em>When you set up </em><strong><em>Active Directory</em></strong><em>, DNS is critical. It translates names to IPs.</em></p><p><em>But what about the reverse? If a system or a log says “who is 10.255.0.101?”, reverse DNS helps translate that IP </em><strong><em>back to the name</em></strong><em>.</em></p><ul><li><em>This is useful in </em><strong><em>network tools</em></strong><em>, </em><strong><em>security logs</em></strong><em>, and </em><strong><em>some integrations</em></strong><em> (like Wazuh or SIEMs).</em></li><li><em>It also makes tools like nslookup return clean results, which is great for troubleshooting.</em></li></ul><h4><strong><em>1. Open DNS Ma</em>nager</strong></h4><p>Go to:<br> Server Manager &gt; Tools &gt; DNS</p><h4>2. Create a Reverse Lookup Zone</h4><ul><li>Right-click Reverse Lookup Zones &gt; New Zone</li><li>Choose Primary Zone</li><li>Select: “This server maintains the zone”</li><li>Choose IPv4 Reverse Lookup Zone</li><li>Enter your network ID: The first 3 octet of your ip addr</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/0*eMG_MINu-0bZ-FGQ" /></figure><ul><li>For example: 10.255.0 → which becomes zone 0.255.10.in-addr.arpa</li><li>Allow only secure updates (or not, depending on lab)</li><li>Finish</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/769/0*mkMpDtf4KNSqCkLJ" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/0*w6hKR4Da1yDyYenO" /></figure><h4>3. Add a PTR Record (<strong>Pointer Record)</strong></h4><ul><li>This maps the IP (e.g., 10.255.0.101) back to a hostname</li><li>Sometimes added automatically when you create A records</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/0*Mt-II9_A9pmbDHP0" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/0*6_VDKd7oMo0thtzH" /></figure><ul><li>If not, you can add it manually under the reverse zone</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/0*RU8BoyZ12f0SkaHw" /></figure><p>Result:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/0*RLD9WfggqFRnXIGc" /></figure><h4>4. Edit Ethernet DNS Settings (Optional but Good Practice)</h4><p>Instead of 127.0.0.1, change the DNS to the server’s real IP:</p><p>10.255.0.101</p><p><strong><em>Why?<br> So when you run nslookup, the system uses the actual network address of the DNS server (your server) instead of the loopback address.</em></strong></p><h4>Steps:</h4><ul><li>Open Server Manager</li><li>Click Local Server (on the left)</li><li>Click the Ethernet link next to “IPv4”</li><li>In the Network Connections window, right-click your active network adapter and choose Properties</li><li>Select Internet Protocol Version 4 (TCP/IPv4) and click Properties</li><li>Under Preferred DNS server, change 127.0.0.1 to 10.255.0.101</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/0*-hu-4Wj7QUdZtO1a" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/0*jSVY4fwc3LBmolDT" /></figure><ul><li><strong>Click OK to save and close all windows</strong></li></ul><h4>Result when you run “nslookup”</h4><p><strong>Instead of:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/0*tPpyWHeBDaeK2ooo" /></figure><p><strong>You’ll now see:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/0*oCs-S-_Ej3_3XUpn" /></figure><h4>Step 7: Create Test Users &amp; Groups</h4><ol><li>Right-click your domain name (e.g., caslab.local) &gt; <strong>New</strong> &gt; <strong>Organizational Unit</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/0*Qh2W-0j61lgve_4x" /></figure><p>2. Create one OU called LagosOU</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/0*8FePGGiEIRLAQR93" /></figure><p>3. Right-click LagosOU &gt; <strong>New</strong> &gt; Organizational Unit</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/0*YYgvI0cklRgg5sL4" /></figure><p>4. Create 2 sub OU: HR and Security</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/0*N1yLYGKO2OBmWYQq" /></figure><p>5. Create users under the sub OU. I am using the Security sub OU.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/0*-PFc557ULQWACauf" /></figure><p>6. Set a password and check “User must change password at next logon” — This is so that the user can adjust their password when they log in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/484/0*z8B2AvEHKclLAOiB" /></figure><p>7. Next &gt;&gt; Finish</p><p>8. Let’s create another user. You can do so by simply clicking the user icon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/0*JMffmtdZJ-y3ENEc" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/0*3GlUDZAsUpc79LQb" /></figure><p>9. Now let’s create a group under this subOU. Right-click the SubOU &gt; New &gt; Group — Called my group CloudSec</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/0*cXEW7uGFIFbr5WQr" /></figure><p>10. Adding members to group: Right-click on user &gt; Add to Group &gt; Advanced &gt; Find Now</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/0*ycvfSZA-b0I6zVTH" /></figure><p><strong>You will also see other groups you can add your user to, such as Administrator.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/0*WQnjXyult9Q-PAUm" /><figcaption>User has been added to the CloudSec Group.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/0*w6lZSdnuYpTQsFG2" /></figure><p><strong><em>Jane Doe was added to the CloudSec group.</em></strong></p><h3>Why This Lab Matters</h3><p>This is the first foundational piece of my home lab, where each component builds into the next.<br> Active Directory with DNS is essential for identity, authentication, and later integrations with monitoring and SIEM tools.</p><h3>What’s Next?</h3><p>The next lab in this <strong>Home Lab Chronicles</strong> series is:</p><blockquote><strong><em>Lab 2: Integrating Imperva DAM with Active Directory</em></strong></blockquote><h3>Reference Videos</h3><p>How to install windows server 2019 — <a href="https://youtu.be/ZjQSuyuN0nA?si=4pz47lfqfCBq1f31">https://youtu.be/ZjQSuyuN0nA?si=4pz47lfqfCBq1f31</a></p><p>Basic configuration tasks in windows server — <a href="https://youtu.be/1nxYJSV7-u8?si=DWMlpfAemzBB6wtn">https://youtu.be/1nxYJSV7-u8?si=DWMlpfAemzBB6wtn</a></p><p>Setting up AD DS with DNS — <a href="https://youtu.be/h3sxduUt5a8?si=4IwHpqRFcyyFhFpV">https://youtu.be/h3sxduUt5a8?si=4IwHpqRFcyyFhFpV</a></p><p>How to create OU, Users, and Groups on AD Domain — <a href="https://youtu.be/cETbT22TWEE?si=fpeGOa4-q5PKkskh">https://youtu.be/cETbT22TWEE?si=fpeGOa4-q5PKkskh</a></p><h3>Final Thoughts</h3><p>If you’re building a home lab for cybersecurity, cloud, or infrastructure — don’t skip AD.<br> It’s not glamorous, but it’s critical.</p><p>Let me know if you try this out or run into any hiccups — I’ll be sharing more labs soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d0bf80e5012" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experience Simulating and Investigating Incidents with NixGuard]]></title>
            <link>https://medium.com/@cassandrachibueze1/my-experience-simulating-and-investigating-incidents-with-nixguard-38b5c6b63900?source=rss-1e1b0b889b0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/38b5c6b63900</guid>
            <dc:creator><![CDATA[Cassandra Chibueze]]></dc:creator>
            <pubDate>Mon, 25 Nov 2024 19:05:17 GMT</pubDate>
            <atom:updated>2024-11-25T19:05:17.058Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>By Cassandra</em></strong></p><p><strong>Introduction</strong></p><p>Cybersecurity is a critical pillar of modern business operations, requiring constant vigilance and effective tools to stay ahead of evolving threats. In this article, I present findings from a simulated investigation undertaken as a cybersecurity analyst, focusing on identifying and mitigating suspicious activities within a company’s network.</p><p>This investigation utilized <strong>NixGuard</strong>, a robust security monitoring and incident management tool designed to provide real-time insights into network traffic, file integrity, and system vulnerabilities. By simulating real-world scenarios in a controlled virtual environment, I evaluated NixGuard’s capabilities in monitoring suspicious patterns, detecting potential threats, and formulating effective incident response plans.</p><p>The project was structured into three core areas:</p><ul><li><strong>Network Analysis:</strong> Monitoring network traffic for unusual patterns and potential threats.</li><li><strong>Threat Detection:</strong> Leveraging NixGuard’s detection capabilities to identify and analyze malware or suspicious files.</li><li><strong>Incident Response Planning:</strong> Developing a response plan to address identified threats effectively.</li></ul><p>This experience provided valuable insights into NixGuard’s potential as a security platform. Below, I outline the steps I took, the findings I observed, and my recommendations for mitigating the identified threats.</p><h3>Tools Used</h3><p>For this simulation, I used the following:</p><ul><li><strong>NixGuard</strong>: I signed up for a 7-day free trial, which provided access to a cloud server and agents for onboarding the NixGuard agent onto my Windows and Linux servers.</li><li><strong>Wazuh Server</strong>: Through the NixGuard trial, I set up a cloud server connected to a Wazuh server, allowing me to monitor logs via a SIEM interface.</li><li><strong>Linux Server</strong>: For hosting NixGuard agent and monitoring logs.</li><li><strong>Windows Server</strong>: For hosting NixGuard agent, simulate threats and analyze files.</li><li><strong>Kali Linux</strong>: For generating simulated attacks.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9TlktamNyX2RQ7oZ" /><figcaption><strong><em>This screenshot illustrates the NixGuard interface following the successful onboarding of the agent, establishing a foundational setup for real-time monitoring and analysis.</em></strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vg-0jBowL57UEQ8N" /><figcaption><strong>This screenshot highlights the Wazuh dashboard, showcasing a summary of alerts categorized by severity, agent activity, endpoint security status, and integrated threat intelligence insights</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*68T1HYbUfUSK-JCe" /><figcaption><strong><em>This screenshot highlights the onboarded agents.</em></strong></figcaption></figure><blockquote>ip of windows server 10.255.0.174</blockquote><blockquote>ip of linux server 10.255.0.149</blockquote><blockquote>ip of kali machine10.255.0.165</blockquote><h3>1. Network Analysis</h3><p>To evaluate network security and test NixGuard’s monitoring capabilities, a brute force attack simulation was conducted using Hydra on a Linux server. The steps involved in setting up and executing this test are as follows:</p><h4>Step 1: Setting Up SSH User</h4><ul><li>Start the SSH Service: Ensure that SSH is enabled and running on the Linux server by executing the following commands:</li></ul><blockquote>sudo<em> systemctl start ssh</em></blockquote><blockquote>sudo<em> systemctl enable ssh</em></blockquote><ul><li><strong>Create a Test User</strong>: A new user named<strong><em> hydratest</em></strong> was created with a known password (<strong><em>password</em></strong>). This user was set up specifically for the test. The command used was:</li></ul><blockquote>sudo adduser hydratest</blockquote><p>Followed by prompts to set up the password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*q6pHkJH8XKDUBfYp" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/0*5C43Q6GDzkAxSpbY" /><figcaption><strong><em>This screenshot shows the hydratest user appearing on the NixGuard map after its creation, confirming that the system effectively tracks user-related activities.</em></strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zV4RyWK3Ff-Xx4lp" /></figure><ul><li><strong>Verify SSH Port Accessibility</strong>: The server’s default SSH port (22) was confirmed open for incoming connections.</li></ul><h4>Step 2: Preparing Hydra on Kali</h4><ul><li><strong>Using RockYou Wordlist</strong>: Instead of a custom password list, the commonly used <strong><em>rockyou.txt</em></strong> wordlist was utilized. This file, pre-installed on Kali Linux, contains a comprehensive list of potential passwords.</li></ul><blockquote>IP address of my attacker machine is <strong>10.255.0.165</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/0*dqEqO5XLahp4Ywd8" /></figure><h4>Step 3: Executing the Hydra Attack</h4><ul><li><strong>Hydra Command Execution</strong>: The Hydra tool was used to attempt brute force login on the Linux server. The command used was:</li></ul><blockquote>hydra -l hydratest -P /usr/share/wordlists/rockyou.txt ssh://10.255.0.149</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/0*RaTUNJDksbWMpXmJ" /><figcaption><em>Hydra systematically tested passwords from the </em><strong><em>rockyou.txt</em></strong><em> file against the hydratest user.</em></figcaption></figure><h4>Observations in NixGuard</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1FjbAOf2rPtPxRMD" /><figcaption>The presence of SSH and PAM activity indicates that NixGuard identified critical services on the monitored endpoint. <strong>SSH</strong> (Secure Shell) is a protocol widely used for secure communication between systems, while <strong>PAM</strong> (Pluggable Authentication Module) relates to the authentication framework managing access for services like SSH. This likely correlates to the brute force testing performed using Hydra, showcasing the detection of login attempts.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_w2rbdcm3Pt2pYYU" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/0*h6KXSOh8m7272TjY" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/0*PxL5yFuxTpTf4Diw" /><figcaption>These 3 screenshots above provide deeper insight into the activity flagged by NixGuard. It highlights the <strong>timestamp</strong> of the event and logs showing multiple failed login attempts with the user “hydratest.” These attempts originate from a specific IP address (<strong>10.255.0.165</strong>) targeting the SSH service (<strong>port 57624</strong>) with the SSH2 protocol. The detection demonstrates NixGuard’s capability to track authentication failures and recognize potential brute-force attacks.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MaY3VaOtAtX8Z9Q0" /><figcaption>The JSON format in this screenshot provides granular details of the detected alert.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8vn9CAMbfJUKmBYP" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*htxOTpxKM6ysFQHr" /></figure><blockquote><strong>The tabular format emphasizes critical data parameters, particularly:</strong></blockquote><blockquote>The alert.full_log, showcasing the repeated failed password attempts with relevant timestamps.</blockquote><blockquote>The alert.rule.groups, identifying the associated categories like “syslog,” “sshd,” and “authentication_failures.”</blockquote><blockquote>The alert.rule.mitre.tactic and technique, linking the activity to “<strong><em>Credential Access” and the specific brute-force method (T1110).</em></strong> These connections reinforce the importance of threat detection methodologies.</blockquote><blockquote>We can also see the user.</blockquote><h3>2. Threat Detection</h3><h4>Objective</h4><p>To analyze suspicious files or malware and verify NixGuard’s capabilities in detecting threats.</p><h4>Findings</h4><p>Two scenarios were tested:</p><ol><li><strong>Linux Environment<br></strong>I simulated suspicious activity by downloading a vulnerable <strong>Apache2</strong> on the Linux server. NixGuard successfully flagged this activity and generated detailed logs identifying the change.</li><li><strong>Windows Environment<br></strong>Using the <strong>EICAR test file</strong>, I simulated malware activity on the Windows server. NixGuard immediately detected the EICAR file deletion in real-time, highlighting the corresponding timestamp, file attributes, and event type.</li></ol><h3>Apache Vulnerability Threat Detection simulation on Linux Environment — Agent (nixag2)</h3><h4><strong>Objective:</strong></h4><p>To evaluate the detection capabilities of NixGuard when installing a vulnerable version of Apache2 on a Linux server.</p><h4>Setup and Steps:</h4><ol><li>Environment Preparation: Target System: Linux Server (10.255.0.149)</li></ol><p>2. Simulated Threat Activity: Installed Apache2 using the command:</p><blockquote><strong>sudo apt install apache2</strong></blockquote><blockquote>The installed version contained known vulnerabilities.</blockquote><h3>Findings:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AOiWw4r0id4DQtPs" /><figcaption>Nix Map flagged the vulnerable Apache installation, displaying vulnerability alerts on its dashboard.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/0*0DFNHtUzmIG5w3W9" /><figcaption>Detailed alert in Nix Map highlighting one vulnerability — CVE-2024–38475</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D0zqZgNbCXUL16fT" /><figcaption>Wazuh detected vulnerabilities during its scan, highlighting high severity alerts in its dashboard.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L9M9R2vuzhDtGCZ_" /><figcaption>This screenshot shows a total of 12 high-severity vulnerabilities flagged on the Linux system.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E-cR098DZgwXQy3u" /><figcaption>This screenshot provides a tabular breakdown of detected vulnerabilities, including CVEs, severity levels, and affected packages (e.g., apache2-data), offering detailed information to help administrators prioritize remediation.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b3RlHPBtPfkQ6__S" /><figcaption>This shows email notification received immediately after installation, summarizing vulnerabilities detected in the Apache installation and their potential impact.</figcaption></figure><blockquote><strong>So generally,this simulation highlights how simply installing a vulnerable application like Apache can result in security alerts from monitoring tools. It demonstrates the importance of vulnerability management and the need for timely patching and upgrades to address known security flaws.</strong></blockquote><blockquote><strong>The Apache installation demonstrated the ability of NixGuard and Wazuh to quickly detect and report vulnerabilities in software packages. Alerts provided sufficient detail for immediate remediation, emphasizing the importance of patching outdated or vulnerable software.</strong></blockquote><h3>EICAR File Threat Detection Test on Windows Environment</h3><h4>Objective:</h4><p>To test NixGuard and Wazuh’s capabilities in detecting and responding to simulated malware activity by downloading the <strong>EICAR test file</strong> on a Windows system. The EICAR file is a standard tool used to test malware detection tools without introducing actual malicious content.</p><h4>Key Steps:</h4><ol><li><strong>Environment Preparation</strong>:</li></ol><ul><li>Antivirus software was disabled on the Windows server to allow the EICAR test file to be downloaded.</li><li>The EICAR file was obtained from the official <strong>EICAR site</strong> and saved to the following path: C:\Users\Administrator\Downloads\eicar.com.</li></ul><p><strong>2. Simulated Threat Activity</strong>:</p><ul><li>The EICAR file was added to the system, triggering monitoring tools to detect and log its activity in real time.</li><li>The focus was on observing alerts generated by NixGuard and Wazuh for this activity.</li></ul><h4>Findings:</h4><ol><li><strong>NixGuard Detection</strong>:</li></ol><p>NixGuard logged the addition of the file (eicar.com) to the system, showing the timestamp (Nov 17, 2024, 06:30:47 PM) and the specific file location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/0*556kLFzZ22ZR4I0e" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wBaQugJr5U9EikKA" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*HFxBipPi4OEXz1Qk" /></figure><blockquote>The EICAR test file was automatically deleted as soon as the real-time antivirus protection was re-enabled. Corresponding logs were generated and sent to both Wazuh and NixGuard, confirming the deletion and ensuring system integrity monitoring.</blockquote><p><strong>2. Wazuh Detection</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PIez7CQcrvo0Ed43" /><figcaption>A Wazuh alert for the EICAR file was received within the timeframe of the activity, indicating immediate detection.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/0*ixX4kGtyV2okhIoo" /></figure><p>This table<strong> </strong>provides further details such as:</p><ul><li><strong>Full Log</strong>: Highlights the event in detail.</li><li><strong>Rule Description</strong>: “Integrity checksum changed.”</li><li><strong>Rule Level</strong>: 7 (Indicates a notable level of concern).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/0*o9zEw9eF62kVUSVV" /></figure><p>This table provides detailed information on the alert in Wazuh’s dashboard, such as:</p><ul><li><strong>MITRE Technique</strong>: Stored Data Manipulation</li><li><strong>File Path</strong>: C:\Users\Administrator\Downloads\eicar.com</li><li><strong>Timestamp:</strong> Nov 17, 2024, 06:30:56.816 PM</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VnKchmLS0dtB3exd" /><figcaption>This screenshot shows a vulnerability detection dashboard summarizing system vulnerabilities. Key highlights include 8 critical, 243 high, 105 medium, and 1 low-severity vulnerabilities. It identifies Microsoft Windows Server 2019 Standard Eval as the most affected OS and highlights CVEs, agents, and packages with vulnerabilities. Visual charts display vulnerability distribution by score, affected OS families (dominated by Windows), and publication year, helping prioritize remediation efforts effectively.</figcaption></figure><blockquote>So generally, this test effectively demonstrated the monitoring tools’ ability to detect and alert on suspicious file activity. The real-time alerts and detailed logs validate the reliability of NixGuard and Wazuh in identifying potential threats and providing actionable information for incident response.</blockquote><h3>3. Incident Response Plan</h3><h4>Objective</h4><p>To outline a comprehensive and actionable plan for addressing and mitigating the identified threats during the investigation.</p><h4>Incident 1: Hydra Brute-Force Attack</h4><p><strong>Response Steps:</strong></p><ul><li><strong>Containment</strong>: Block the source IP address at the firewall level to stop further brute-force attempts.</li><li><strong>Eradication</strong>: Review all potentially compromised accounts, change their passwords, and enforce account lockout policies for repeated failed login attempts.</li><li><strong>Recovery</strong>: Enable secure login mechanisms and continuously monitor for unusual login patterns or residual brute-force activity.</li><li><strong>Mitigation</strong>: Implement rate limiting for login attempts and integrate CAPTCHAs or multi-factor authentication (MFA) to prevent future attacks.</li></ul><h4>Incident 2: Apache2 Vulnerable Installation on Linux</h4><p><strong>Response Steps:</strong></p><ul><li><strong>Containment</strong>: Disconnect or isolate the Linux server from the network to avoid exploitation of the detected vulnerabilities.</li><li><strong>Eradication</strong>: Verify the source of the installed Apache package, remove unauthorized or outdated packages, and patch the system by upgrading Apache to a secure version.</li><li><strong>Recovery</strong>: Restore the server’s functionality by configuring secure settings and re-integrating it into the network. Conduct a thorough security review to ensure no residual vulnerabilities remain.</li><li><strong>Mitigation</strong>: Implement monitoring for package downloads, enforce strict package-signing policies, and automate vulnerability scanning to detect outdated software.</li></ul><h4>Incident 3: EICAR File Download and Deletion on Windows Server</h4><p><strong>Response Steps:</strong></p><ul><li><strong>Containment</strong>: Upon detection of the EICAR test file, ensure that real-time antivirus is activated, quarantine the file, and check for any other suspicious files.</li><li><strong>Eradication</strong>: Remove the test file from the system and conduct a full malware scan to ensure no additional malicious files are present.</li><li><strong>Recovery</strong>: Validate the integrity of system-critical files and restore full server functionality. Confirm the effectiveness of antivirus policies.</li><li><strong>Mitigation</strong>: Strengthen malware detection protocols, conduct regular integrity checks, and train users on handling suspicious downloads.</li></ul><h4>Conclusion</h4><p>The incidents demonstrated the efficacy of NixGuard and Wazuh in real-time detection and alert generation. The response plan provides a clear framework for containment, eradication, recovery, and mitigation of future threats. It is crucial to continuously refine security policies, upgrade software, and enforce best practices to maintain a robust defense against potential risks.</p><p><strong>Thank you for reading this far! If you’d like to try it out, NixGuard offers a 7-day free trial, and it’s quite self-explanatory to set up. My report can also serve as a guide to get you started.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38b5c6b63900" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unleashing Zeek: A Step-by-Step Install Guide to Powerful Network Monitoring.]]></title>
            <link>https://medium.com/@cassandrachibueze1/unleashing-zeek-a-step-by-step-install-guide-to-powerful-network-monitoring-aac1e999b6b?source=rss-1e1b0b889b0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/aac1e999b6b</guid>
            <category><![CDATA[network-monitoring]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[packet-analysis]]></category>
            <category><![CDATA[network-analysis]]></category>
            <dc:creator><![CDATA[Cassandra Chibueze]]></dc:creator>
            <pubDate>Sun, 02 Jul 2023 21:55:42 GMT</pubDate>
            <atom:updated>2023-07-02T21:55:42.632Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*8Dja1sA6qHZi_Q-O_7CNvA@2x.jpeg" /></figure><p>Zeek is primarily a security monitoring tool that thoroughly examines all traffic on a network link to identify any suspicious activity. It also offers a wide range of traffic analysis capabilities beyond just security-related tasks. These include performance measurements and aiding in troubleshooting network issues.</p><p>Zeek has built-in features for various analysis and detection tasks, such as detecting malware through external registries, reporting vulnerable software versions on the network, identifying popular web applications, detecting SSH brute-force attacks, and validating SSL certificate chains.</p><p>Let’s dive right into the installation steps…</p><p>For this, I will be installing as the root user.</p><p>1. To switch to the root user, run the command:</p><p><em>note: The user password will be asked for; type the password and press enter.</em></p><pre>sudo su —</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/204/1*oRjTw6zsCY6utralxMds8Q.png" /></figure><p>2. Add the repository link:</p><pre>echo ‘deb http://download.opensuse.org/repositories/security:/zeek/Debian_12/ /’ | sudo tee /etc/apt/sources.list.d/security:zeek.list</pre><p>3. Download the trusted keys:</p><pre>curl -fsSL https://download.opensuse.org/repositories/security:zeek/Debian_12/Release.key | gpg — dearmor | sudo tee /etc/apt/trusted.gpg.d/security_zeek.gpg &gt; /dev/null</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UyMA8t1_3YXXvLXM38ds9Q.png" /></figure><p>4. Update the mirrors:</p><pre>sudo apt update -y</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/838/1*L74jbyYlh-dEgIg_MI75bQ.png" /></figure><p>5. Install Zeek:</p><pre>sudo apt install zeek -y</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*tK716eKwE23ks1o1wrEcDQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*ZpwIyt3ffIz3dFoQm__RzA.png" /></figure><p>After installing Zeek with the steps above, Head to this site referenced below for steps on how to run the installed Zeek.</p><p>Reference: <a href="https://docs.zeek.org/en/master/quickstart.html">https://docs.zeek.org/en/master/quickstart.html</a></p><p>Here’s a quick summary:</p><ul><li>Firstly, note the installation directory of Zeek. (Installation directory: /opt/zeek/)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*W2pSWR92kq3OzdbfXLrPgg.png" /></figure><ul><li>Check the network interface cards’ name using the command: #ip a</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/471/1*ukKUdIeduNCbwjpT7RAkkg.png" /></figure><ul><li>Check the Zeek configuration file, using these commands:</li></ul><pre>“cd /opt/zeek/etc”<br>ls</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*8__yX4NYgUSEEhunjMqvnw.png" /></figure><ul><li>Open the file “node.cfg”, to edit using the command: nano node.cfg</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/308/1*lbkl8rY9RZhVEWPbNIgQoA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*seWHzIap2o3A2s-KqoUGzw.png" /></figure><ul><li>Now that is checked and confirmed, press the following commands below to exit the editor.</li></ul><p><strong>- Ctrl + x</strong></p><p>- <strong>Type “n”, if you made no changes.</strong></p><p>-<strong> Type “y”, if you made changes. Followed by “Enter” key.</strong></p><p>6. Now, navigate back to the “bin” directory.</p><ul><li>Note the current path using the command: #pwd</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/1*pqQbL0HlIp-R6xsv3_IF4Q.png" /></figure><ul><li>Then go back one step with the command #cd ..</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/309/1*77m-TnuQhiMMruuVwHrBxQ.png" /></figure><ul><li>Use the command “ls” to list the contents of current directory</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/461/1*g1cwqd9bJPX5SP1eNhA0bQ.png" /></figure><ul><li>Now go to “bin” directory using #cd bin</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*WE_shY95H5z0HjHWrgRD1A.png" /></figure><ul><li>Confirm your are in the “bin” directory using #ls and #pwd.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*xp57WVfnuo9Xpt-0DRQvvQ.png" /></figure><p>7. Now start the ZeekControl shell like this:</p><pre>#./zeekctl</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*OWiSZAQbPQuJmd8cEb9Q_A.png" /></figure><ul><li>Since this is the first time using the shell, perform an initial installation of the ZeekControl configuration:</li></ul><pre>[ZeekControl] &gt; install</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*f09k8bfRkCCS0pBAScRiFw.png" /></figure><ul><li>Then start up a Zeek instance with command:</li></ul><pre>[ZeekControl] &gt; start</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/244/1*I_cyb_u9j8uBkpzQkWA4Ig.png" /></figure><ul><li>To stop the zeek instance, type:</li></ul><pre>[ZeekControl] &gt; stop</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*qHwhuzlREwGRt-1g0pPnQw.png" /></figure><ul><li>Exit the zeekctl command screen by typing:</li></ul><pre>[ZeekControl] &gt; exit</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/1*TwKuK3Jz1J-guKLOiTtHhQ.png" /></figure><p><strong><em>NOTE: To be able to run the Zeek command from any directory, you can do the following:</em></strong></p><pre>#echo “export PATH=/opt/zeek/bin:$PATH” &gt;&gt; ~/.profile<br><br>#source ~/.profile</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*imOWT4amJ1ChPElr2GwUXA.png" /></figure><blockquote><strong>Note: Be mindful of the syntax when copying commands from a word document especially if there are signs and symbols with that command. The recommended way is to type the command.</strong></blockquote><p><strong>Zeek Log files.</strong></p><ul><li>Navigating to the Zeek log directory. Use the command below:</li></ul><pre>cd /opt/zeek/logs/</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/316/1*9AJS0P0EhuEFlGa_XfkNKQ.png" /></figure><ul><li>Use the commands “pwd” and “ls” to confirm you are in the correct directory.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*IZSbbx4Owo9lxC_a5xknOQ.png" /></figure><ul><li>To view the latest log files, go to the “current” directory.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*SB5tQN1yAwoUnwJ09SWGrA.png" /></figure><ul><li>The directory with a “date” name stores the archive of previously captured logs. Navigate as shown in the screenshot below.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V2EMP24sw0l0IhbmRs3MKA.png" /></figure><ul><li>The “current” directory has the below log files once your capture has started.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TNXoi7lCO1oZ8lIZDn8IZQ.png" /></figure><blockquote><strong><em>NOTE: When you begin the capture, more log files will be seen too. It’s not restricted to these alone. Log files such as Conn.log, Http.log, Dns.log, etc would also be seen.</em></strong></blockquote><p><strong><em>Also, note that ZEEK can be used against LIVE TRAFFIC and not only historical traffic</em></strong></p><p>With the use of certain commands, you can force Zeek to bend to your will.</p><p>Congratulations! You have your Zeek up and running. Defend away! 😀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aac1e999b6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>