<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Incident Response on Everything Cyber</title><link>https://everything-cyber.netlify.app/tags/incident-response/</link><description>Recent content in Incident Response on Everything Cyber</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 15 Feb 2025 20:49:58 +0530</lastBuildDate><atom:link href="https://everything-cyber.netlify.app/tags/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>Incident Response with Velociraptor</title><link>https://everything-cyber.netlify.app/blog/velociraptor/</link><pubDate>Sat, 15 Feb 2025 20:49:58 +0530</pubDate><guid>https://everything-cyber.netlify.app/blog/velociraptor/</guid><description>Incident Response Training Lab with Velociraptor Description This project simulates a real-world cybersecurity incident investigation using Velociraptor.
Environment Setup Virtual Machines Velociraptor Server: Ubuntu Server (4 GB RAM, 2 CPUs) windows endpoint: Windows 10 Workstation (4 GB RAM, 2 CPUs) Attack Machine: Kali Linux Machine (4 GB RAM, 2 CPUs) Note: Set the VM&amp;rsquo;s Networking to NAT, so that the machines can ping each other or in the same network</description></item></channel></rss>