<?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 Aditya Yadav on Medium]]></title>
        <description><![CDATA[Stories by Aditya Yadav on Medium]]></description>
        <link>https://medium.com/@4ghora?source=rss-db2a6b8380f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kYbcZrVH6KRfBpfr00Ie9g.jpeg</url>
            <title>Stories by Aditya Yadav on Medium</title>
            <link>https://medium.com/@4ghora?source=rss-db2a6b8380f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:57:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@4ghora/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[IBM Security QRadar Functions and Capabilities]]></title>
            <link>https://medium.com/@4ghora/ibm-security-qradar-functions-and-capabilities-2eff8212a3e7?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2eff8212a3e7</guid>
            <category><![CDATA[basics]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[qradar]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[notes]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Fri, 31 May 2024 06:27:18 GMT</pubDate>
            <atom:updated>2024-05-31T06:27:18.993Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*bVRo_TpAJ5lIBG2tlCRauw.png" /></figure><h3>QRadar Basic Concepts</h3><h4>Understanding SIEM Solutions and QRadar</h4><ul><li>SIEM : Security Operations and Event Management</li><li>Centralized location for all the security data in one place.</li><li>Collects events, flows and security data like logs and threat intelligence feeds.</li><li>Correlates the data (Finding relationship between data)</li><li>Generates alerts in real time</li><li>Provides security reports and perform forensics.</li></ul><h4>Log Manager Vs. SIEM</h4><ul><li>Log Manager has far less features then a SIEM solution.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*SL4weE0ptZepd514TXqFtQ.png" /></figure><h4>QRadar Overview</h4><ul><li>QRadar is a tool that centralizes security information and output for the user.</li><li>QRadar receives events and security data from a verity of sources, like firewall, databases, web servers, network traffic etc.</li><li>QRadar uses a combination of correlation of techniques to generate output. Like getting and alert when an anomaly is detected, getting reports showing security level of company. generate compliance reports and can be used for threat hunting.</li></ul><h4>QRadar Sources of Information</h4><ul><li>Log Sources : Operational System, Firewall/Proxy, Databases.</li><li>Flow Sources : Network Listening, NetFlow, QFlow</li><li>Vulnerability Scans : Qradar VM, External Integrations</li><li>Asset Information : Asset Weighting, Network Hierarchy, Manual Input</li><li>Watch Lists : Blacklists, HR Feeds, Manual Input</li><li>Threat Intelligence : IBM X-Force, Third-Party Intel</li></ul><h3>QRadar Architecture Overview</h3><h4>QRadar Components</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*lNdAX-zD_WB1yDM_mNFK3A.png" /></figure><ul><li>Top right corner, log sources.</li><li>Bottom right corner, network flow sources like servers, routers, switches etc.</li><li>Those information sources provide data to the collectors, both event and flow collector.</li><li>Data then is provides to processors by the collectors. Sometimes we have data node.</li><li>Console is the device users interact with, mostly there is one console in per deployment. Console is responsible for managing all other devices.</li><li>In real life deployment, there can be multiple processors and collectors.</li></ul><h4>Event Collector</h4><ol><li>Collects events from log sources.</li><li>Normalize the logs, meaning that it extracts the information from the raw log and puts the information into predefined fields. such as timestamp, source IP, destination IP etc.</li><li>Map logs to QIDs (Qradar identifiers). QIDs are events like successful or failed authentication etc.</li><li>Bundles similar events to save space also known as event coalescing.</li><li>Forward to event processor</li></ol><h4>Event Processor</h4><ol><li>Receive normalized and raw logs from collector</li><li>Store events (if data-node not present)</li><li>Correlate with other events/information (Finding connections between different events)</li><li>Identify behavioral changes and policy violations for the event.</li><li>Distribute the information with other components. (if applicable)</li><li>Send the events to magistrate component (console)</li></ol><h4>Flow Collector</h4><p><strong>Collect Flows </strong>from different flow sources, such as:</p><ul><li>Network taps</li><li>span ports</li><li>NetFlow</li><li>VFlow</li><li>QFlow</li></ul><p><strong>Normalize Flows</strong> (Flow collector extracts the main information from the raw network and then puts them in a normalized way)</p><p>Forward to flow processor (Collector then forwards the data to the flow processor)</p><h4>Flow Processor</h4><ol><li>Receive normalized and raw flows from collector</li><li>Store events (if data-note not present)</li><li>Correlate with other flow/evets</li><li>Identify behavioral changes and policy violations for the flow</li><li>Distribute the information (if applicable)</li><li>Send the flows to the magistrate components</li></ol><h4>Data Node</h4><ul><li>Both event processor and flow processors can be integrated with the data node</li><li>Adds storage and processing capacity to event/flow processors</li><li>Increase the search speed</li></ul><h4>Console</h4><ul><li>Used to connect to QRadar everytime.</li><li>Provides user web interface</li><li>an analyst will never connect to processor or collector directly, will always connect to console.</li><li>Manages other hosts in environment</li><li>Real-time view of events, flows, offenses and everything else</li></ul><p><strong>Includes the magistrate</strong></p><ul><li>Service responsible for core processing components</li><li>views, reports, alerts and analysis.</li><li>Custom rules</li></ul><h4>App Host</h4><ul><li>QRadar provides additional functionalities through extensions (called apps)</li><li>Example : User Behavioural Analytics</li><li>Apps run on console, App host is required because some heavy apps may require a lot of processing power.</li><li>App Host Contains all the apps installed in the environment.</li><li>Reduce the impact on the console</li></ul><h4>Vulnerability Scanner</h4><ul><li>Responsible for actively scan servers for vulnerabilities</li><li>Provide vulnerability information for correlation</li><li>Serveral Configuration parameters, to scan the server according to the users wants without affecting servers performance.</li></ul><h4>QRadar Components — Data Flow</h4><ul><li>The Log sources generates the logs, Which is then collected by the event collector and normalize the logs, then assign a QID, and send them to the event processor.</li><li>The event processor receives the normalized logs, process them, apply behavioral rules, and then stores them, which in this case are being stored in the data node.</li><li>The events are now available for the Magistrate on the for the custom rules processing.</li><li><strong>Now Let’s take a look at flow part</strong></li><li>Let’s say a collector is listening on the network traffic, every second 100’s of flows are generated and which are then collected by flow collector, it normalizes the flows and send them to flow processor.</li><li>Flow processor stores flows locally, since there is no data node. Processor also tries to identify behavioral anomalies and forward the data to the magisrtator if needed.</li></ul><h3>QRadar Architecture Examples</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*0tqTGHuzySooLd-QW8hqkw.png" /></figure><ul><li>Multiple Collectors and processors all connected to console to help distribute the load across several components and would provide segregation between environments.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*kiPgQREzsGLCqWHHn-QDqA.png" /></figure><ul><li>Here we have 2 event collectors with 1 event processor</li><li>A good example of this would be a client that has 2 data centers with low volume of events per second.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*KUPg46_T5R8c3V1ZN88JLQ.png" /></figure><ul><li>Idea here is having all qradar components in one single box.</li><li>Common in small and medium companies that have a low amount of events and flows.</li><li>Qradar has a component called all in one box, which can perform all the tasks of different components like collection, processing and user interface.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*etORVIrhRDFWDwBIbV6RCQ.png" /></figure><ul><li><strong>Multitentancy : Having multiple clients in one qradar environment.</strong></li><li>Instead of having multiple environments for each client, user can have one environment with one console which can manage multiple event/flow processor and collectors.</li><li>Data from each client is isolated from each other.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*lKzflkB6fAbXd4nF2o0lTg.png" /></figure><ul><li>Basically QRadar appliances are hosted on cloud, IBM takes care for everything including patching. Console is on the cloud so it can be accessed from anywhere around the world.</li><li>So, let say a we have a client with few log sources and few flow sources. User has to install some data gateways in client environment and configure them to normalize and forward the data to the cloud.</li></ul><h3>Additional Components Overview</h3><h4>Vulnerability Manager</h4><ul><li>Actively scan assets looking for known vulnerabilities.</li><li>Provide asset information for the asset database.</li><li>Can be integrated with several other vulnerability management solutions like Nessus, Qualys etc.</li></ul><h4>Risk Manager</h4><ul><li>Monitor device configurations like switches, Routers, Firewalls etc.</li><li>Network change simulations</li><li>Vulnerability exploitation assessment</li><li>Use data from : Firewalls, Routers, Switches, IDS/IPS systems etc.</li></ul><h4>Incident Forensics</h4><ul><li>In-depth incident forensics.</li><li>Retrace step-by-step actions of an attacker</li><li>Reconstruct data in a security attack</li></ul><h4>IBM QRadar Apps</h4><ul><li>Expand the QRadar functionalities by using QRadar apps. Example : User behaviour analytics app</li><li>IBM Security AppExchange</li><li>Provide several apps for your QRadar. User behavior app, Health Check app, pulse app for good dashboards.</li></ul><h4>QNI ( QRadar Network Insights )</h4><ul><li>Used for monitoring network packets in the environment.</li><li>Expands the network monitoring capabilities</li><li>Provide full packet inspection</li><li>Application level packet inspection to better malware detection, phishing emails and data exfiltration.</li></ul><h4>IBM X-Force Intelligence Feed</h4><ul><li>Provide threat intelligence to the SIEM like blacklisted IPs and attack signatures.</li><li>Used in event correlation and blacklisting like creating an alert when server tries to communicate with an IP classified as malicious.</li><li>Provide data for incident investigation. For example if you see a suspicious IP user can perform search in X-Force database to verify if its malicious or not.</li></ul><h3>Data Collection</h3><h4>Event Collection</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*OkfeSmbPI0CilB7W7-UOGQ.png" /></figure><ul><li>Event Collector is responsible for collecting logs from log sources. This collection can be a push or pull collection.</li><li><strong>Push Collection : </strong>Log sources send the logs to QRadar. In this situation QRadar is listening for incoming logs. A good example is syslog protocol.</li><li><strong>Pull Collection : </strong>QRadar has to retrieve the logs from the log sources. For example if we have a app which saves log on the disk, we can use qradar to connect to the server and download the logs.</li><li>Once event collector has the logs, then they are parsed by a DSM.</li></ul><h4>DSM ( Device Support Modules)</h4><ul><li>Plugins for log collection (Parsers)</li><li>Normalize raw logs into meaningful fields</li><li>Over 400 log types supported.</li><li>Customs DSM’s can be developed as per organisations need.</li></ul><h4>Syslog Protocol</h4><ul><li>Most used protocol for log collection. Majority of devices support syslog.</li><li>The idea here is having one standard protocol for log transmission.</li><li>Generated by the log sources and send to collector (push-collection)</li><li>Port 514 UDP (or TCP)</li></ul><h4><strong>Windows Log Sources</strong></h4><ul><li>do not support syslog protocol natively, windows logs can be collected in three ways :</li><li><strong>Syslog Agents : </strong>converts windows logs into syslog and forward to qradar. Push-Collection, Examples : Snare, Winlogd, Kiwi</li><li><strong>Windows Security Event Logs(MSRPC) : </strong>Enables QRadar to connect to the server via RPC and collect security logs. Pull-Collection, Credentials required. Might Experience delays.</li><li><strong>WinCollect Agent : </strong>Agents managed by qradar that collects logs from the windows sources and send through syslog to qradar. Push-collection.</li></ul><h4>Other Collection Methods</h4><ul><li><strong>SSH or FTP : </strong>Connect to the server and download the file.</li><li><strong>Database Connectors (JDBC) : </strong>Here we use JDBC connection to connect to a database and then the log table.</li><li><strong>OPSEC/LEA : </strong>Another standard for log collection.</li><li><strong>REST API’s : </strong>Can be used to retrieve logs from our applications.</li><li>TLS Syslog : Encrypted version of syslog.</li></ul><p><strong>Information From Security Devices</strong></p><ul><li><strong>Firewall : </strong>TCP connections, Dropped packets, Config. changes</li><li><strong>IDS/IPS : </strong>Policy violations, attack attempts, dropped connections.</li><li><strong>Proxy : </strong>Browsing history, HTTP connections, Exfiltration attempts.</li><li><strong>Auth. Devices : </strong>Authentication logs, Access level changes, Access logs</li><li><strong>Anti-Virus : </strong>Server infections, User behavior, Malware outbreaks</li><li>End Point Agents : USB logs, Browsing history, Access logs</li></ul><h3>Flow Collection</h3><ul><li>Flows contain all the data transmitted to the applications.</li></ul><h4>Network Listening</h4><p>Provide full flow inspection/information</p><ul><li>Header and partial contents</li></ul><p>Similar to TCP dump</p><ul><li>Parsed and normalized by QRadar, so it can be easilt searched later</li><li>QRadar does not provide full network inspection.</li></ul><p>Can be achieved through</p><ul><li>Network taps : Listening to packets on the physical network interface of QRadar</li><li>Span ports : AKA Packet mirroring, Idea here is to confgure routers and switches to forward all the traffic to one of the Qradar network ports.</li></ul><h4>Flow Information Forwarding</h4><ul><li>If Network listening is not possible on your environment, then flow information forwarding can get you the information.</li><li>Idea here is to configure network devices and firewalls to send information to QRadar.</li></ul><p><strong>Only provides flow headers</strong></p><ul><li>Source, destination, port, flow, size, etc.</li></ul><p><strong>Does not provide full packet inspection</strong></p><ul><li>No access to the body of the packet.</li></ul><p>Main Collection methods : Netflow, Jflow, Sflow</p><h3>Vulnerability Scans</h3><ul><li>provide qradar a snapshot of the risk of the environment. or it provides vulnerability information and detailed server information to QRadar, so an analyst can have a better picture during an incident.</li></ul><h4>Vulnerability Scanner</h4><ul><li>Scanner can scan almost all components like servers, virtual machines, routers, laptops, desktops and applications.</li><li>Qradar can do authenticated and on authenticated scans.</li><li>Un-authenticated scan is like black box testing.</li><li>authenticared scans require crendentials to allow qradar to connect to devices. Qradar can analyze not only the services that have open ports, but also services that are not available externally.</li></ul><h4>External Integrations</h4><ul><li>Qradar can be integrated with your existing vulnerability solution. Can be done by API’s And Manua Import</li><li>Suppoted Solutions : Qualys, Nessus, Nmap, etc</li></ul><h4>Information Provided</h4><ul><li>Vulnerability Information : Based on up-to-date vulnerability database.</li><li>Port scan information : Helps on incident/forensics.</li><li>Asset discovery : Find Hosts on your network</li><li>Asset information : Software installed, servies running, Accounts.</li></ul><h3>Events</h3><ul><li>Events are message generated by machines or logs generated by servers and applications.</li><li>Events provide information about things that happen in the environment and help us detect threats and anomalies.</li><li>Event collection is mandatory under PCI and SOX standards.</li></ul><h4>What is an event?</h4><ul><li>A message received from a log source.</li></ul><p>Examples of an Event</p><ul><li>One failed authentication attempt on a windows server.</li><li>A packet droped by a firewall</li><li>A new process that has been started</li></ul><h4>What is In a Event?</h4><ul><li>Structure is based siem solution provider, mostly structure seems like this: Timestamp, Severity, Source and destination, Process ID, User, Log Message</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*NMj-_XOgdZtTDJQF_OXPfg.png" /></figure><h4>Importance of Raw Logs</h4><ul><li>Provide access to original message.</li><li>Can be source of extra information not contained in the normalized logs.</li><li>Essential for compliance (PCI, SOX, etc)</li></ul><h4>Coalescing Event</h4><ul><li>log collection can be tricky task, we want to collect all logs without overloading the system. For anomaly can cause dos (denial of service) by making server create millions of logs in short time.</li><li>QRadar has a feature named coalescing events, so avoid upper situation from happening.</li><li>Combine similar events during bursts.</li><li>if 3+ events in less than 10 seconds with same properties like same (QID, Source IP, Destination IP and Username)</li><li>QRadar keeps the first 3 events, and aggregate the rest in one single event.</li></ul><h3>Event Properties</h3><h4>QID — QRadar Identifiers</h4><ul><li>Map events to unique identifiers</li><li>Provide standardization</li><li>Facilitate on correlation</li></ul><p>Examples:</p><ul><li>59500166 : Server backup started</li></ul><p>This QID is related to server backups, when a server backup log is generated, that log is associated to this QID. To find the log use this QID and apply timestamp or timeframe in search.</p><ul><li>69251825 : Start Batch Backup</li><li>11001168 : LDAP host unavailable</li></ul><h4>Timestamps</h4><p>There are 3 different types of timestamps:</p><ul><li><strong>Log Source Time : </strong>The time on the log source when the event happend. This field is parsed from the logs.</li><li><strong>Start Time : </strong>The time the event reached the QRadar collector. Time at the beginning of the event processing pipeline.</li><li><strong>Storage Time : </strong>The time the event was written out to the disk. Time at the end of the event processing pipeline.</li></ul><h4>Magnitude</h4><p>Means criticality of an offense and it is calculated on 3 parameters:</p><ul><li><strong>Relevance : The impact of the offence in the network.</strong></li><li><strong>Credibility : </strong>How much you can “trust on the logs”</li><li><strong>Severity : </strong>Level of threat considering how prepared the destination is</li></ul><h3>Additional Information On Events</h3><p>Qradar extracts events from logs. There are 3 types of properties.</p><ul><li><strong>Normalized Properties : </strong>Qradar defaults, similar across DSM’s. Example: Source IP, Destination IP, Timestamps</li><li><strong>Standard Custom Properties : </strong>Out of the box, For specific log sources. Examples: URL (Proxy Logs), Virus Name(AV Logs)</li><li><strong>User Custom Properties : </strong>Created by the user, Regex based. Examples : Memory Usage (Linux), Disk Usage(Windows)</li></ul><h4>Property Indexing</h4><ul><li>Qradar can index the main event properties to improve search speed.</li><li>Main properties are indexed by default. Like Source/Destination IP, Log Source, Event name and many more.</li><li>Enable indexing for custom properties.</li><li>Create searches/reports based on indexed properties.</li></ul><h4>Data Obfuscation</h4><ul><li>Logs may contain sensitive information like Social Insurance Numbers, Health card numbers.</li><li>Admins can configure data obfuscation. Like hide the value, Example : 442-***-***-156</li><li>To view obfuscated data request permission from the admin</li><li>Best practice is to not have any sensitive information in the logs.</li></ul><h4>Network Hierarchy</h4><ul><li>Network Information</li><li>Network Severity</li><li>Network ranges</li></ul><h4>Asset Details</h4><ul><li>Asset owners</li><li>Asset prioritization</li><li>Open ports</li><li>Mac addresses</li></ul><h3>Ariel Query Language (AQL)</h3><ul><li>Used to extract information that may not be available on the user interface. Dirrect access to log/flow database.</li><li>Used in event/flow searches</li><li>Used for external integration</li><li>Similar to sql</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*HR8zP9_0ljlkIIOrHtsBPg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*0YY_lvdmROKByxjEmO9uJQ.png" /></figure><h3>Understanding Flows</h3><ul><li>A record of the network activity that can last for seconds, minutes or days.</li><li>details of a specific traffic</li><li>Not full packets inspection, but keep in initial packets.</li></ul><p>Examples of a flows:</p><ul><li>A user requesting a website.</li><li>A user streaming a movie.</li><li>An authentication request to a remote ssh server.</li></ul><h4>What is In a Flow?</h4><ul><li>Contains information about the source and destination ip</li><li>Mac’s and source and destination ports, Protocols being used</li><li>Flows also contains the flow size, which is the amount of data being transmitted.</li><li>Contains timestamps</li><li>Partial Data</li></ul><h4>Flow Collection Types</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*dHYh5jdHNhV4v-y0ov1-5A.png" /></figure><h4>Importance of Raw Flows</h4><p>Contains the original information transmitted</p><p>May contain details of the traffic</p><ul><li>URLs, Username, etc.</li></ul><p>Can be used to identify tunneling</p><ul><li>Using one protocol to transmit other information</li><li>Example: Using the HTTP protocol to access a SSH server.</li></ul><h3>Flow Properties</h3><h4>Timestamps</h4><ul><li><strong>First Packet Time</strong> : Time the flow started.</li><li><strong>Last Packet Time : </strong>Time the flow finished.</li><li><strong>Storage Time : </strong>Time the flow was processed and stored on disk.</li></ul><h3>Understanding Offenses</h3><h4>What is an Offense?</h4><p>A unified threat from a specific source</p><ul><li>Group of related incidents to the same threat actor</li></ul><p>Fed by several data sources like:</p><ul><li>Events</li><li>Flows</li><li>Vulnerabilities</li><li>etc.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*KKN_V8Hx6wxSML0s4zlFUg.png" /></figure><h4>How an offense is generated?</h4><ul><li>One or more triggered rules</li><li>correlation if a similar offense is open</li></ul><p>Example : Brute-force attack</p><p>(Rule: 7 failed login attempts in less than 10 mins)</p><ul><li>Step 1 : Rule Violated</li><li>Step 2 : A new event is created</li><li>Step 3 : Generated alerts (if enabled)</li><li>Step 4 : Check open similar offenses</li><li>If yes : update the original offense including extra information</li><li>If no : create new offense</li></ul><h4>Correlation Engines</h4><ul><li><strong>Custom Rule Engine (CRE)</strong></li><li>Rule based, created by the SIEM administrator. “If X then Y”</li></ul><p>Example :</p><p>Brute force attack : “If more than 7 failed login attempts in less than 10 mins, then generate an offense”</p><ul><li><strong>Anomaly Detection Engine (ADE)</strong></li><li>Based on anomalies, behaviors and thresholds. “If X is presenting abnormalities then Y”</li></ul><p>Example :</p><p>Data exfiltration: “If the network utilization of a user is 75% above the last 2 month average, then generate an offense”</p><h3>Offense Properties</h3><h4>Main Properties</h4><ul><li><strong>Description and categories</strong> : related to threat.</li><li><strong>Magnitude</strong> : based on several factors.</li><li><strong>Event/Flow Count</strong> : Counter showing the number of events and flows related to the offense</li><li><strong>Source and Destination</strong> : related to threat,</li><li><strong>Network</strong> : Good description of the networks related to the offense.</li><li><strong>Users</strong> : might contain which users were effected by the threat.</li></ul><h4>Timestamps</h4><ul><li><strong>Start Time</strong> : Means when the threat was first observed.</li><li><strong>Last Event </strong>: Tells you when the last event or flow was observed. Useful to understand if attack is still happening of stopped.</li><li><strong>Duration : </strong>for example — for how long an attacker was trying t brute force an account.</li></ul><h4>Magnitude</h4><ul><li>Magnitude of an offense is calculated similarly to events, it’s also based on the relevance, severity and credibility.</li><li>Offense considers way more data when calculating those components and including the volume of events, the vulnerability of data and the network that the target is in.</li></ul><h4>Event Magnitude</h4><ul><li>Related to a single event, Based on event information</li></ul><p>Example :</p><ul><li>Brute force attack — Magnitude 6</li><li>Privilege escalation — Magnitude 7.5</li></ul><h4>Offense Magnitude</h4><ul><li>Related to the whole offense, Based on events, flows, assets, networks.</li><li>Very complex algorithm</li></ul><p>Example:</p><ul><li>Successful brute-force attack followed by privilage escalation — Magnitude 9</li></ul><h4><strong>Qradar — Offense Statuses</strong></h4><ul><li><strong>Open (active)</strong> : When an offense is generated, it is automatically marked as active or open.</li><li><strong>Inactive </strong>: If an offense doesn’t receive updates or events in a certain period of time. It is marked as inactive.</li><li><strong>Hidden </strong>: Non-relevant events are marked hidden.</li><li><strong>Protected : Users alerts or offenses cannot be closed by someone else.</strong></li><li>Closed : Closing an offense.</li></ul><h3>Understanding Rules</h3><p>The rules are responsible for correlating data such as events and flows, into threats to be investigated.</p><h4>What is a rule?</h4><ul><li>A set of conditional statements that trigger an action/response. Like “If X happens do Y”.</li></ul><p>Example :</p><ul><li>If more than 7 ‘failed authentication’ event observed in less than 10 mins, generate an offense. (CRE Rule)</li><li>If the network traffic increases in 200%, generate an alert (ADE Rule).</li></ul><h4>What is Building Block?</h4><p>A set of conditions that characterizes a group or behavior.</p><ul><li>A rule with no action, just for classification purposes.</li><li>If the event id = ‘X’ or ‘Y’ then the event is characterized as ‘A’</li><li>Start with BB:___</li></ul><p>Example:</p><ul><li>If the network traffic is on the tcp port 80 or 443, then classify the traffic as “user browsing”</li><li>If server hostname contains “*main” then classify the server as “mail server”.</li></ul><h4>BB:HostDefination</h4><ul><li>Pre-defined building block to retain information about server and environment.</li><li>Usually updated automatically by Qradar.</li></ul><p>Examples:</p><ul><li>BB:HostDefination:Proxy Servers</li><li>BB:HostDefination:LDAP Servers</li><li>BB:HostDefination:DMZ Asssets</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*SgtdhdB1FCWcTv0GesAhgA.png" /></figure><h4>Reference Sets</h4><ul><li>Store a list of information.</li><li>Useful on rules that require dynamic information</li></ul><p><strong>Examples:</strong></p><ul><li>List of employees on vacation.</li><li>List all VIP users</li><li>Blacklisted IPs</li><li>Whitelisting</li></ul><p>Can be populated through api’s</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*3rM4nCK_3yBVEpr3qMhDeQ.png" /></figure><h4>Response Delimiters</h4><p>A rule can trigger multiple times in a minute.</p><ul><li>Example : Firewall configuration change</li></ul><p>A response delimiter avoids multiple responses.</p><p>Example : One email per day per firewall device.</p><h3>Rule Types</h3><h4>Custom Rule Engines</h4><ul><li><strong>Event-based Rules</strong> : Consider information only from events.</li><li><strong>Flow-based Rules</strong> : Consider information only from network traffic.</li><li><strong>Common-based Rules</strong> : Correlate information from network traffic and events.</li><li><strong>Offense-based Rules</strong> : Consider information from offenses.</li></ul><h4>Anomaly Detection Engine (ADE)</h4><ul><li>Anomaly-based Offenses : Identify abnormal activity on events or flows</li></ul><p>Example : if the network traffic is 50% higher than in the average of the last week, generate an alert.</p><ul><li>Behavior-based Offenses : Test events/flows for volume changes in behavior that occur in seasonal patterns.</li></ul><p>Example : If a mail server present a anomaly behavior, generate an offense.</p><ul><li>Threshold-based Offenses : Identify anomalous behavior by pre-set thresholds.</li></ul><p>Example : If there are more than 5 active VPN connections between 9pm and 6 am, generate an offense</p><h3>Understanding Assets</h3><h4>What is an asset?</h4><ul><li>Any device on your network</li><li>Physical or virtual assets</li><li><strong>Asset weight</strong></li></ul><p>— Helps on magnitude calculation</p><h4>Asset Database</h4><ul><li>Contains all IT-related assets</li></ul><p>— Relevant to security</p><ul><li>Can be managed automatically and manually</li><li>Should be continuously managed</li><li>if not managed properly, analysts will waste lots of time on trying to figure out what an asset is.</li></ul><h4>Sources of Asset Information</h4><ul><li><strong>User Interface : </strong>Ui is provided to analyst to provide data manually.</li><li><strong>Events</strong> : Qradar can automatically gather data from events such as logs from http serves or authentication servers. Logs contain lots of information like IPs, Usernames, Hostnames, Mac addresses etc.</li><li><strong>Flows</strong> : Contains crucial information like IPs, open ports, etc.</li><li><strong>Vulnerability scanners</strong> : Most preferred way to gather information.</li></ul><h4>Asset Groups</h4><ul><li>Helps to organize the assets.</li><li>Used in reports and rules</li><li>Subgroups</li></ul><h4>Main Properties of Assets</h4><ul><li><strong>IP Address &amp; Mac Address</strong> : Used as unique identifiers for an asset.</li><li><strong>Network Segment</strong> : Helps in classify threat and priority.</li><li><strong>Open Ports &amp; Vulnerabilities</strong> : Can be used to identify threat in the network.</li><li><strong>Asset Weight</strong> : Criticality of the asset for the organization.</li><li><strong>Operating System</strong> : Asset profile also provide information about the operating system.</li><li>Contact details : Assets database contains contact information for the server.</li></ul><h3>Understanding Reports And Dashboard</h3><h4>Qradar Report</h4><ul><li>A document that consolidates data.</li><li>Unusually tailored for high level audiences like managers and executives.</li><li>Contains static data.</li><li>Pre-defined time range like daily, monthly, quarterly, yearly.</li><li>Example : High-risk users (monthly)</li></ul><h4>Qradar Dashboard</h4><ul><li>A screen that consolidates data.</li><li>Usually tailored for operations.</li><li>Contains dynamic data.</li><li>Usually contains real-time data.</li><li>Example : Latest threat dashboard.</li></ul><h3>Report Basics</h3><h4>Understanding Reports</h4><ul><li>Consolidated data from several data sources.</li><li>Understand big picture (understand trends in the data so we can be proactive on upcoming trends)</li><li>Out of the box reports</li></ul><p>— Basic security reports</p><p>— Compliance reports (PCI, SOX, ISO)</p><p>Custom Reports or customize existing reports.</p><h4>Data Sources</h4><p>Reports can have data from:</p><ul><li><strong>Raw events and flows</strong></li><li>Normalized events and flows</li><li>Aggregated data</li><li>Vulnerability scans</li><li>Datasets and threat intelligence</li></ul><h4><strong>Reports and Saved Searches</strong></h4><ul><li>A report can contain one or more sections</li><li>Each section is independent from each other</li><li>Each section is independent saved search.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*gh2lHieCGp16uI2Md17Heg.png" /></figure><h4>Report Output Formats</h4><ul><li><strong>PDF</strong></li><li>XLS</li><li>CSV (does not support charts and graphics, only supports tables)</li><li>XML</li><li>RTF</li><li>HTML</li></ul><h3>Dashboards</h3><ul><li>A centralized place for monitoring</li><li>Independent widgets (saved searches)</li><li>Private or shared dashboards</li><li>Near real time information</li><li>Aggregated information</li><li>Can show you system alerts</li></ul><h4>Default Dashboards</h4><ul><li><strong>Applications Overview</strong> : Shows information about the applications on your environment. Like network traffic per application, applications are generating more logs, top servers denied by firewall.</li><li><strong>Compliance Overview</strong> : related to compliance performance indicators such as top failed authentications by users, top usernames involved in compliance rule breaches, top source IPs related to compliance breaches.</li><li><strong>Network Overview</strong> : It shows information about the network such as top talkers, firewall denies, link utilization, network traffic by port, etc.</li><li><strong>System Monitoring Dashboard</strong> : holistic information about qradar system environment. event processors utilization, flow rate, tag log sources, system notifications.</li><li><strong>Threat/Security Monitoring</strong> : Several threat indicators such as top alarm from IDS/IPS, top systems attacked, most severe offenses</li></ul><h4>Saved Searches</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*-uWMpm17FuzUfwM4Y59FfQ.png" /></figure><ul><li>Can be used for searching in real time.</li><li>Can also be used in reports.</li><li>They are also a base for dashboards, each dashboard is composed of several widgets.</li><li>Each widget is saved search that queries the database and show us the information we want.</li><li>Saved searches are base for lot of things and can be reused across several artifacts.</li></ul><h4>Custom Dashboards</h4><ul><li>Customized out of the box dashboards</li><li>Create dashboard from zero</li><li>Based on saved searches</li><li>can reutilize widgets from other dashboards.</li><li>Can be private or shared.</li></ul><h4>System Notifications</h4><ul><li>Gives you real time information about system anomalies like High CPU/memory, New unkown log sources</li><li>Admins can set thresholds, Like if disk utilization is more than 90% then generate an alert.</li></ul><h3>Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*Ql7fECudiN44o0klaTs6aA.png" /></figure><p>Will see you with a new blog on how to Monitor and Detect with IBM Security QRadar.</p><p>Till then have fun kids!!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2eff8212a3e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tools For Phishing Analysis]]></title>
            <link>https://medium.com/@4ghora/tools-for-phishing-analysis-fa5c54711cd1?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa5c54711cd1</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[phishing]]></category>
            <category><![CDATA[techniques]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Sun, 14 Apr 2024 12:28:40 GMT</pubDate>
            <atom:updated>2024-04-14T12:28:40.687Z</atom:updated>
            <content:encoded><![CDATA[<h3>Email Header Analysis</h3><ul><li><strong>Messageheader</strong>: <a href="https://toolbox.googleapps.com/apps/messageheader/analyzeheader">https://toolbox.googleapps.com/apps/messageheader/analyzeheader</a></li><li><strong>Message Header Analyzer</strong>: <a href="https://mha.azurewebsites.net/">https://mha.azurewebsites.net/</a></li><li><strong>Mail Header </strong>: <a href="https://mailheader.org/">https://mailheader.org/</a></li></ul><h4>The tools below can help you analyze information about the sender’s IP address:</h4><ul><li>IPinfo.io: <a href="https://ipinfo.io/">https://ipinfo.io/</a></li><li>URLScan.io: <a href="https://urlscan.io/">https://urlscan.io/</a></li><li>You can use other tools that provide the same functionality and more, such as <a href="https://www.url2png.com/">URL2PNG</a> and <a href="https://www.wannabrowser.net/">Wannabrowser</a>.</li><li>Talos Reputation Center: <a href="https://talosintelligence.com/reputation">https://talosintelligence.com/reputation</a></li></ul><h3>Email Body Analysis</h3><ul><li>URL Extractor: <a href="https://www.convertcsv.com/url-extractor.htm">https://www.convertcsv.com/url-extractor.htm</a></li><li><a href="https://gchq.github.io/CyberChef/">https://gchq.github.io/CyberChef/</a></li><li>Talos File Reputation: <a href="https://talosintelligence.com/talos_file_reputation">https://talosintelligence.com/talos_file_reputation</a></li><li>VirusTotal: <a href="https://www.virustotal.com/gui/">https://www.virustotal.com/gui/</a></li></ul><h3>Malware Sandbox</h3><ul><li>Hybrid Analysis: <a href="https://www.hybrid-analysis.com/">https://www.hybrid-analysis.com/</a></li><li>Any.Run: <a href="https://app.any.run/">https://app.any.run/</a></li><li><a href="https://www.joesecurity.org/">https://www.joesecurity.org/</a></li></ul><h3>Automated Phishing Analysis</h3><p>Phishtool : <a href="https://www.phishtool.com/">https://www.phishtool.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa5c54711cd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Phishing Artifact Collection Checklist]]></title>
            <link>https://medium.com/@4ghora/phishing-artifact-collection-checklist-c4282679be43?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4282679be43</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[checklist]]></category>
            <category><![CDATA[phishing]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Sun, 14 Apr 2024 10:33:57 GMT</pubDate>
            <atom:updated>2024-04-14T10:33:57.029Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fc5Hty43PF-xduWZ" /><figcaption>Photo by <a href="https://unsplash.com/@kasiade?utm_source=medium&amp;utm_medium=referral">Kasia Derenda</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Below is a checklist of the pertinent information an analyst (you) is to collect from the email header:</p><ul><li>Sender email address</li><li>Sender IP address</li><li>Reverse lookup of the sender IP address</li><li>Email subject line</li><li>Recipient email address (this information might be in the CC/BCC field)</li><li>Reply-to email address (if any)</li><li>Date/time</li></ul><p>Afterward, we draw our attention to the email body and attachment(s) (if any).</p><p>Below is a checklist of the artifacts an analyst (you) needs to collect from the email body:</p><ul><li>Any URL links (if an URL shortener service was used, then we’ll need to obtain the real URL link)</li><li>The name of the attachment</li><li>The hash value of the attachment (hash type MD5 or SHA256, preferably the latter)</li></ul><p><strong>Warning</strong>: Be careful not to click on any links or attachments in the email accidentally.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4282679be43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DFIR]]></title>
            <link>https://medium.com/@4ghora/dfir-9a62ff786c2f?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a62ff786c2f</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[forensics]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Sat, 16 Mar 2024 12:15:19 GMT</pubDate>
            <atom:updated>2024-03-16T12:15:19.809Z</atom:updated>
            <content:encoded><![CDATA[<h4>DFIR stands for Digital Forensics and Incident Response. This field covers the collection of forensic artifacts from digital devices such as computers, media devices, and smartphones to investigate an incident. This field helps Security Professionals identify footprints left by an attacker when a security incident occurs, use them to determine the extent of compromise in an environment, and restore the environment to the state it was before the incident occurred.</h4><h4>The need for DFIR</h4><p>DFIR helps security professionals in various ways, some of which are summarized below:</p><ul><li>Finding evidence of attacker activity in the network and sifting false alarms from actual incidents.</li><li>Robustly removing the attacker, so their foothold from the network no longer remains.</li><li>Identifying the extent and timeframe of a breach. This helps in communicating with relevant stakeholders.</li><li>Finding the loopholes that led to the breach. What needs to be changed to avoid the breach in the future?</li><li>Understanding attacker behavior to pre-emptively block further intrusion attempts by the attacker.</li><li>Sharing information about the attacker with the community.</li></ul><h4>Who performs DFIR?</h4><p>As the name suggests, DFIR requires expertise in both Digital Forensics and Incident Response. Dividing these two fields this way, the following skillset is needed to become a DFIR professional:</p><ul><li><strong>Digital Forensics: </strong>These professionals are experts in identifying forensic artifacts or evidence of human activity in digital devices.</li><li><strong>Incident Response: </strong>Incident responders are experts in cybersecurity and leverage forensic information to identify the activity of interest from a security perspective.</li></ul><p>DFIR professionals know about Digital Forensics and cybersecurity and combine these domains to achieve their goals. Digital Forensics and Incident Response domains are often combined because they are highly interdependent. Incident Response leverages knowledge gained from Digital Forensics. Similarly, Digital Forensics takes its goals and scope from the Incident Response process, and the IR process defines the extent of forensic investigation.</p><h3>Basic concepts of DFIR</h3><h4>Artifacts:</h4><p>Artifacts are pieces of evidence that point to an activity performed on a system. When performing DFIR, artifacts are collected to support a hypothesis or claim about attacker activity. For example, if we are to claim that the attacker used Windows registry keys to maintain persistence on a system, we can use the said registry key to support our claim. In this case, the mentioned registry key will be considered an artifact. Artifact collection is, therefore, an essential part of the DFIR process. Artifacts can be collected from the Endpoint or Server’s file system, memory, or network activity.</p><h4>Chain of custody:</h4><p>Another critical aspect of maintaining the integrity of evidence is the chain of custody. When the evidence is collected, it must be made sure that it is kept in secure custody. Any person not related to the investigation must not possess the evidence, or it will contaminate the chain of custody of the evidence.</p><h4>Order of volatility:</h4><p>Digital evidence is often volatile, i.e., it can be lost forever if not captured in time. For example, data in a computer system’s memory (RAM) will be lost when the computer is shut down since the RAM keeps data only as long as it remains powered on. Some sources are more volatile as compared to others. For example, a hard drive is persistent storage and maintains the data even if power is lost.</p><h4>Timeline creation:</h4><p>Once we have collected the artifacts and maintained their integrity, we need to present them understandably to fully use the information contained in them. A timeline of events needs to be created for efficient and accurate analysis. This timeline of events puts all the activities in chronological order. This activity is called timeline creation.</p><h3>DFIR Tools</h3><h4>Eric Zimmerman’s tools:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/140/0*ZcyTQHiUZNAGx-Nl.jpg" /></figure><p>Eric Zimmerman is a security researcher who has written a few tools to help perform forensic analysis on the Windows platform. These tools help the registry, file system, timeline, and many other analyses.</p><h4>KAPE:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/0*GmrR0h8uinhA02z0.png" /></figure><p>Kroll Artifact Parser and Extractor (KAPE) is another beneficial tool by Eric Zimmerman. This tool automates the collection and parsing of forensic artifacts and can help create a timeline of events.</p><h4>Autopsy:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*u7wA4MWtcLvaqcRO.jpg" /></figure><p>Autopsy is an open-source forensics platform that helps analyze data from digital media like mobile devices, hard drives, and removable drives. Various plugins for autopsy speed up the forensic process and extract and present valuable information from the raw data sources.</p><h4>Volatility:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*hvdUOL1nso6MEfwn.jpg" /></figure><p>Volatility is a tool that helps perform memory analysis for memory captures from both Windows and Linux Operating Systems. It is a powerful tool that can help extract valuable information from the memory of a machine under investigation.</p><h3>Redline:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*IzG1hZfRcOQ00gu_.jpg" /></figure><p>Redline is an incident response tool developed and freely distributed by FireEye. This tool can gather forensic data from a system and help with collected forensic information.</p><h4>Velociraptor:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/217/0*bqL-hNOD3Vi_Yad5.png" /></figure><p>Velociraptor is an advanced endpoint-monitoring, forensics, and response platform. It is open-source but very powerful.</p><h3>The Incident Response process</h3><p>In Security Operations, the prominent use of Digital Forensics is to perform Incident Response.</p><p>SANS has published an <a href="https://www.sans.org/white-papers/33901/">Incident Handler’s handbook</a>. The handbook defines the steps as follows:</p><ol><li>Preparation</li><li>Identification</li><li>Containment</li><li>Eradication</li><li>Recovery</li><li>Lessons Learned</li></ol><p>As described above, they are identical to the steps defined by NIST.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fD3iiMe_IQV-6PsA.png" /></figure><ol><li><strong>Preparation</strong>: Before an incident happens, preparation needs to be done so that everyone is ready in case of an incident. Preparation includes having the required people, processes, and technology to prevent and respond to incidents.</li><li><strong>Identification</strong>: An incident is identified through some indicators in the identification phase. These indicators are then analyzed for False Positives, documented, and communicated to the relevant stakeholders.</li><li><strong>Containment</strong>: In this phase, the incident is contained, and efforts are made to limit its effects. There can be short-term and long-term fixes for containing the threat based on forensic analysis of the incident that will be a part of this phase.</li><li><strong>Eradication</strong>: Next, the threat is eradicated from the network. It has to be ensured that a proper forensic analysis is performed and the threat is effectively contained before eradication. For example, if the entry point of the threat actor into the network is not plugged, the threat will not be effectively eradicated, and the actor can gain a foothold again.</li><li><strong>Recovery</strong>: Once the threat is removed from the network, the services that had been disrupted are brought back as they were before the incident happened.</li><li><strong>Lessons Learned</strong>: Finally, a review of the incident is performed, the incident is documented, and steps are taken based on the findings from the incident to make sure that the team is better prepared for the next time an incident occurs.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a62ff786c2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Types Of Cyber Attacks On Each OSI Layer]]></title>
            <link>https://medium.com/@4ghora/types-of-cyber-attacks-on-each-osi-layer-6bebd10460df?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bebd10460df</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cybercrime]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[network]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Sat, 16 Mar 2024 06:51:14 GMT</pubDate>
            <atom:updated>2024-03-16T06:51:14.598Z</atom:updated>
            <content:encoded><![CDATA[<h3>Layer 1 — Physical:</h3><h4>Traffic eavesdropping</h4><ul><li>Unauthorized interception of network traffic.</li></ul><h3>Layer 2 — Data Link:</h3><h4>MAC spoofing</h4><ul><li>Falsifying MAC address to impersonate another device.</li></ul><h4>ARP spoofing</h4><ul><li>Manipulating ARP tables to redirect traffic.</li></ul><h4>VLAN hopping</h4><ul><li>Exploiting VLAN configuration to gain unauthorized access.</li></ul><h4>DHCP spoofing</h4><ul><li>Providing false DHCP responses to redirect traffic.</li></ul><h4>Rogue access points</h4><ul><li>Unauthorized access points installed to intercept network traffic.</li></ul><h3>Layer 3 — Network:</h3><h4>IP spoofing</h4><ul><li>Falsifying IP addresses to impersonate other devices.</li></ul><h4>Manipulating routing tables</h4><ul><li>Altering routing information to redirect traffic.</li></ul><h4>ICMP redirect</h4><ul><li>Redirecting traffic using falsified ICMP redirect messages.</li></ul><h4>DDoS attacks</h4><ul><li>Overwhelming a target with excessive traffic (TCP/UDP flood, SYN flood, Smurf attack).</li></ul><h3>Layer 4 — Transport:</h3><h4>Lateral Movement</h4><ul><li>Unauthorized movement within a network.</li></ul><h4>Port scanning</h4><ul><li>Scanning for open ports on target devices.</li></ul><h4>DNS poisoning</h4><ul><li>Manipulating DNS records to redirect traffic.</li></ul><h4>DDoS attacks</h4><ul><li>Overwhelming a target with excessive traffic (TCP/UDP flood).</li></ul><h3>Layer 5 — Session:</h3><h4>Access control bypass</h4><ul><li>Circumventing access controls to gain unauthorized access.</li></ul><h4>Adversary-in-the-middle attack</h4><ul><li>Intercepting and altering communication between two parties.</li></ul><h3>Layer 6 — Presentation:</h3><h4>Cracking encryption</h4><ul><li>Decrypting encrypted data without authorization.</li></ul><h4>Injection attacks</h4><ul><li>Inserting malicious code or commands into data inputs.</li></ul><h4>File inclusion vulnerabilities</h4><ul><li>Exploiting vulnerabilities to include unauthorized files.</li></ul><h4>Cross-site scripting (XSS)</h4><ul><li>Injecting malicious scripts into web pages viewed by other users.</li></ul><h4>Cross-site request forgery (CSRF)</h4><ul><li>Forcing users to execute unwanted actions on a web application where they are authenticated.</li></ul><h3>Layer 7 — Application:</h3><h4>Phishing</h4><ul><li>Deceiving users into providing sensitive information.</li></ul><h4>Password cracking</h4><ul><li>Attempting to guess or decrypt passwords.</li></ul><h4>Buffer overflow</h4><ul><li>Exploiting software vulnerabilities to execute malicious code.</li></ul><h4>Format string attack</h4><ul><li>Exploiting vulnerabilities in input validation to execute arbitrary code.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bebd10460df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Incident handling with Splunk]]></title>
            <link>https://medium.com/@4ghora/incident-handling-with-splunk-efd9ed7ede0e?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/efd9ed7ede0e</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[investigation]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Fri, 15 Mar 2024 09:54:47 GMT</pubDate>
            <atom:updated>2024-03-15T09:54:47.710Z</atom:updated>
            <content:encoded><![CDATA[<p>An incident from a security perspective is “Any event or action, that has a negative consequence on the security of a user/computer or an organization is considered a security incident.” Below are a few of the events that would negatively affect the environment when they occurred:</p><ul><li>Crashing the system</li><li>Execution of an unwanted program</li><li>Access to sensitive information from an unauthorized user</li><li>A Website being defaced by the attacker</li><li>The use of USB devices when there is a restriction in usage is against the company’s policy</li></ul><h3><strong>Incident Handling Life Cycle</strong></h3><p>As an Incident Handler / SOC Analyst, we would aim to know the attackers’ tactics, techniques, and procedures. Then we can stop/defend/prevent against the attack in a better way. The Incident Handling process is divided into four different phases. Let’s briefly go through each phase before jumping into the incident, which we will be going through in this exercise.</p><p><strong>1. Preparation</strong></p><p>The preparation phase covers the readiness of an organization against an attack. That means documenting the requirements, defining the policies, incorporating the security controls to monitor like EDR / SIEM / IDS / IPS, etc. It also includes hiring/training the staff.</p><p><strong>2. Detection and Analysis</strong></p><p>The detection phase covers everything related to detecting an incident and the analysis process of the incident. This phase covers getting alerts from the security controls like SIEM/EDR investigating the alert to find the root cause. This phase also covers hunting for the unknown threat within the organization.</p><p><strong>3. Containment, Eradication, and Recovery</strong></p><p>This phase covers the actions needed to prevent the incident from spreading and securing the network. It involves steps taken to avoid an attack from spreading into the network, isolating the infected host, clearing the network from the infection traces, and gaining control back from the attack.</p><p><strong>4. Post-Incident Activity / Lessons Learnt</strong></p><p>This phase includes identifying the loopholes in the organization’s security posture, which led to an intrusion, and improving so that the attack does not happen next time. The steps involve identifying weaknesses that led to the attack, adding detection rules so that similar breach does not happen again, and most importantly, training the staff if required.</p><h3>Incident Handling: Scenario</h3><h4><strong>Interesting log Sources</strong></h4><p>Some of the interesting log sources that will help us in our Investigation are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IbyTFVDqZMgKg63a43YI8A.png" /></figure><h3>Reconnaissance Phase</h3><p>Reconnaissance is an attempt to discover and collect information about a target. It could be knowledge about the system in use, the web application, employees or location, etc.</p><h3><strong>Exploitation Phase</strong></h3><p><strong>http_method</strong> will give us information about the HTTP Methods observed during these HTTP communications.</p><p>To see what kind of traffic is coming through the POST requests, we will narrow down on the field http_method=POST</p><p>The term Joomla is associated with the webserver found in a couple of fields like<strong> uri, uri_path, http_referrer</strong>, etc. This means our webserver is using Joomla CMS (Content Management Service) in the backend.</p><p>form_data The field contains the requests sent through the form on the admin panel page, which has a login page.</p><p>| table _time uri src dest_ip form_data to create a table containing important fields as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*amA-1WPbi0FV7rMSJzpTbQ.png" /></figure><h4><strong>Extracting Username and Passwd Fields using Regex</strong></h4><p><strong>rex field=form_data &quot;passwd=(?&lt;creds&gt;\w+)&quot;</strong> To extract the <strong>passwd</strong> values only. This will pick the <strong>form_data</strong> field and extract all the values found with the field. <strong>creds</strong>.</p><h3>Installation Phase</h3><h4><strong>Was this file executed on the server after being uploaded?</strong></h4><p>Following the Host-centric log, sources were found to have traces of the executable 3791. exe.</p><ul><li>Sysmon</li><li>WinEventlog</li><li>fortigate_utm</li></ul><p>For the evidence of execution, we can leverage sysmon and look at the EventCode=1 for program execution.</p><p><strong>Findings:</strong></p><ul><li>A malicious executable file 3791.exe was observed to be uploaded by the attacker.</li><li>We looked at the sysmon logs and found the MD5 hash of the file.</li></ul><h3><strong>Action on Objective:</strong></h3><p>After compromising the web server, the attacker defaced the website.</p><p><strong>Findings:</strong></p><ul><li>We examined the logs and found the file name used to deface the webserver.</li></ul><h3><strong>Weaponization Phase:</strong></h3><p>We used various threat Intel platforms to find the attacker’s infrastructure based on the following information we saw in the above activities.</p><p>Information we had:</p><p>Domain: prankglassinebracket.jumpingcrab.com</p><p>IP Address: 23.22.63.114</p><p><strong>Findings:</strong></p><ul><li>Multiple masquerading domains were found associated with the attacker’s IPs.</li><li>An email of the user Lillian.rose@po1s0n1vy.com was also found associated with the attacker&#39;s IP address.</li></ul><h3><strong>Deliver Phase:</strong></h3><p>In this phase, we again leveraged online Threat Intel sites to find malware associated with the adversary’s IP address, which appeared to be a secondary attack vector if the initial compromise failed.</p><p><strong>Findings:</strong></p><ul><li>A malware name MirandaTateScreensaver.scr.exe was found associated with the adversary.</li><li>MD5 of the malware was c99131e0169171935c5ac32615ed6261</li></ul><h3><strong>Hybrid-Analysis</strong></h3><p>Hybrid Analysis is a beneficial site that shows the behavior Analysis of any malware. Here you can look at all the activities performed by this Malware after being executed. Some of the information that Hybrid-Analysis provides are:</p><ul><li>Network Communication.</li><li>DNS Requests</li><li>Contacted Hosts with Country Mapping</li><li>Strings</li><li>MITRE ATT&amp;CK Mapping</li><li>Malicious Indicators.</li><li>DLLs Imports / Exports</li><li>Mutex Information if created</li><li>File Metadata</li><li>Screenshots</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*NZ2kapAM5RLb4rQd.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efd9ed7ede0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Entry Level Splunk]]></title>
            <link>https://medium.com/@4ghora/entry-level-splunk-7913a63f0a26?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7913a63f0a26</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[splunk]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Wed, 13 Mar 2024 05:27:49 GMT</pubDate>
            <atom:updated>2024-03-13T05:27:49.985Z</atom:updated>
            <content:encoded><![CDATA[<h3>Splunk Components</h3><p>Splunk has three main components, namely Forwarder, Indexer, and Search Head. These components are explained below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*HdArUYyUD6HeDuG5.png" /></figure><h4><strong>Splunk Forwarder</strong></h4><p>Splunk Forwarder is a lightweight agent installed on the endpoint intended to be monitored, and its main task is to collect the data and send it to the Splunk instance. It does not affect the endpoint’s performance as it takes very few resources to process. Some of the key data sources are:</p><ul><li>Web server generating web traffic.</li><li>Windows machine generating Windows Event Logs, PowerShell, and Sysmon data.</li><li>Linux host generating host-centric logs.</li><li>Database generating DB connection requests, responses, and errors.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*TDVykiOrMOPH27n8.png" /></figure><h4><strong>Splunk Indexer</strong></h4><p>Splunk Indexer plays the main role in processing the data it receives from forwarders. It takes the data, normalizes it into field-value pairs, determines the datatype of the data, and stores them as events. Processed data is easy to search and analyze.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*oCklo879B6TpfscL.png" /></figure><h4><strong>Search Head</strong></h4><p>Splunk Search Head is the place within the Search &amp; Reporting App where users can search the indexed logs as shown below. When the user searches for a term or uses a Search language known as Splunk Search Processing Language, the request is sent to the indexer and the relevant events are returned in the form of field-value pairs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZzWgYQ_F88s_EA4D.png" /></figure><p>Search Head also provides the ability to transform the results into presentable tables, visualizations like pie-chart, bar-chart and column-chart, as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/0*xNGk9WhOfHoz5oZ0.png" /></figure><h3>Navigating Splunk</h3><h4><strong>Splunk Bar</strong></h4><p>When you access Splunk, you will see the default home screen identical to the screenshot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7UzPzPNB8g8aJrlU.png" /></figure><p>Let’s look at each section, or panel, that makes up the home screen. The top panel is the <strong>Splunk Bar </strong>(below image).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nniDZtQBabGDfSnL.png" /></figure><p>In the Splunk Bar, you can see system-level messages (<strong>Messages</strong>), configure the Splunk instance (<strong>Settings</strong>), review the progress of jobs (<strong>Activity</strong>), miscellaneous information such as tutorials (<strong>Help</strong>), and a search feature (<strong>Find</strong>).</p><p>The ability to switch between installed Splunk apps instead of using the <strong>Apps panel</strong> can be achieved from the Splunk Bar, like in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/367/0*1JA_OjZKgwtHQOHc.png" /></figure><h4><strong>Apps Panel</strong></h4><p>Next is the <strong>Apps Panel</strong>. In this panel, you can see the apps installed for the Splunk instance.</p><p>The default app for every Splunk installation is <strong>Search &amp; Reporting</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/272/0*k_Zi-JC8U7b1_JkG.png" /></figure><h4><strong>Explore Splunk</strong></h4><p>The next section is <strong>Explore Splunk</strong>. This panel contains quick links to add data to the Splunk instance, add new Splunk apps, and access the Splunk documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/0*VwJNBh5TWFCYHPQf.png" /></figure><h4><strong>Splunk Dashboard</strong></h4><p>The last section is the <strong>Home Dashboard</strong>. By default, no dashboards are displayed. You can choose from a range of dashboards readily available within your Splunk instance. You can select a dashboard from the dropdown menu or by visiting the <strong>dashboards listing page</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N2BDUw1nBykLxcRD.gif" /></figure><p>You can also create dashboards and add them to the Home Dashboard. The dashboards you create can be viewed isolated from the other dashboards by clicking on the <strong>Yours</strong> tab.</p><p>Please review the Splunk documentation on Navigating Splunk <a href="https://docs.splunk.com/Documentation/Splunk/8.1.2/SearchTutorial/NavigatingSplunk">here</a>.</p><h4>Adding Data</h4><p>Splunk can ingest any data. As per the Splunk documentation, when data is added to Splunk, the data is processed and transformed into a series of individual events.</p><p>The data sources can be event logs, website logs, firewall logs, etc.</p><p>Data sources are grouped into categories. Below is a chart listing from the Splunk documentation detailing each data source category.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SzqXIOthCYM1_6no.png" /></figure><p>In this room, we’re going to focus on <strong>VPN logs</strong>. When we click on the Add Data link (from the Splunk home screen), we&#39;re presented with the following screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/0*N_TDtkdJvesRnHc5.png" /></figure><p>We will use the Upload Option to upload the data from our local machine. Download the attached log file and upload it on Splunk.</p><p>As shown above, it has a total of 5 steps to successfully upload the data.</p><ol><li><strong>Select Source</strong> -&gt; Where we select the Log source.</li><li><strong>Select Source Type </strong>-&gt; Select what type of logs are being ingested.</li><li><strong>Input Settings</strong> -&gt;Select the index where these logs will be dumped and hostName to be associated with the logs.</li><li><strong>Review</strong> -&gt; Review all the gif</li><li><strong>Done </strong>-&gt; Final step, where the data is uploaded successfully and ready to be analyzed.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*evyPjP-9qHXREluc.gif" /></figure><p>As you can see, there are <strong>A LOT</strong> more logs we can add to the Splunk instance, and Splunk supports various source types.</p><p>Download the attached log file “VPN_logs” and upload this file into the Splunk instance with the right source type.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7913a63f0a26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Investigating with ELK 101]]></title>
            <link>https://medium.com/@4ghora/investigating-with-elk-101-44a9173e7cf4?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/44a9173e7cf4</guid>
            <category><![CDATA[elastic]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Tue, 12 Mar 2024 18:35:44 GMT</pubDate>
            <atom:updated>2024-03-12T18:35:56.840Z</atom:updated>
            <content:encoded><![CDATA[<h3>EQL Investigating with ELK 101</h3><h3>Elastic Stack Overview</h3><p>Elastic stack is the collection of different open source components linked together to help users take the data from any source and in any format and perform a search, analyze and visualize the data in real-time.</p><h4><strong>Elasticsearch</strong></h4><p>Elasticsearch is a full-text search and analytics engine used to store JSON-formated documents. Elasticsearch is an important component used to store, analyze, perform correlation on the data, etc. Elasticsearch supports RESTFul API to interact with the data.</p><h4><strong>Logstash</strong></h4><p>Logstash is a data processing engine used to take the data from different sources, apply the filter on it or normalize it, and then send it to the destination which could be Kibana or a listening port. A logstash configuration file is divided into three parts, as shown below.</p><p>The <strong>input</strong> part is where the user defines the source from which the data is being ingested.</p><p>The <strong>filter</strong> part is where the user specifies the filter options to normalize the log ingested above.</p><p>The Output part is where the user wants the filtered data to send. It can be a listening port, Kibana Interface, elasticsearch database, a file, etc.</p><h4><strong>Beats</strong></h4><p>Beats is a host-based agent known as Data-shippers that is used to ship/transfer data from the endpoints to elasticsearch. Each beat is a single-purpose agent that sends specific data to the elasticsearch. All available beats are shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*EsYyv9LGzo0wz2nV.png" /></figure><h4><strong>Kibana</strong></h4><p>Kibana is a web-based data visualization that works with elasticsearch to analyze, investigate and visualize the data stream in real-time. It allows the users to create multiple visualizations and dashboards for better visibility — more on Kibana in the following tasks.</p><p><strong>How they work together:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ApoVjacsgJaLUUQ_.png" /></figure><ul><li>Beats is a set of different data shipping agents used to collect data from multiple agents. Like Winlogbeat is used to collect windows event logs, Packetbeat collects network traffic flows.</li><li>Logstash collects data from beats, ports or files, etc., parses/normalizes it into field value pairs, and stores them into elasticsearch.</li><li>Elasticsearch acts as a database used to search and analyze the data.</li><li>Kibana is responsible for displaying and visualizing the data stored in elasticsearch. The data stored in elasticseach can easily be shaped into different visualizations, time charts, infographics, etc., using Kibana.</li></ul><p>Kibana Discover tab is a place where analyst spends most of their time. This tab shows the ingested logs (also known as documents), the search bar, normalized fields, etc. Here analysts can perform the following tasks:</p><ul><li>Search for the logs</li><li>Investigate anomalies</li></ul><h3><strong>Discover Tab</strong></h3><p>Discover tab within the Kibana interface contains the logs being ingested manually or in real-time, the time-chart, normalized fields, etc. Analysts use this tab mostly to search/investigate the logs using the search bar and filter options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Icw6Uzv-C_7E2Z2q0Mh1A.png" /></figure><p>Some key information available in a dashboard interface are</p><ol><li><strong>Logs (document):</strong> Each log here is also known as a single document containing information about the event. It shows the fields and values found in that document.</li><li><strong>Fields pane</strong>: Left panel of the interface shows the list of the fields parsed from the logs. We can click on any field to add the field to the filter or remove it from the search.</li><li><strong>Index Pattern:</strong> Let the user select the index pattern from the available list.</li><li><strong>Search bar:</strong> A place where the user adds search queries / applies filters to narrow down the results.</li><li><strong>Time Filter:</strong> We can narrow down results based on the time duration. This tab has many options to select from to filter/limit the logs.</li><li><strong>Time Interval: </strong>This chart shows the event counts over time.</li><li><strong>TOP Bar: </strong>This bar contains various options to save the search, open the saved searches, share or save the search, etc.</li></ol><h4><strong>Index Pattern</strong></h4><p>Kibana, by default, requires an index pattern to access the data stored/being ingested in the elasticsearch. <strong>Index pattern</strong> tells Kibana which elasticsearch data we want to explore. Each Index pattern corresponds to certain defined properties of the fields. A single index pattern can point to multiple indices.</p><p>Each log source has a different log structure; therefore, when logs are ingested in the elasticsearch, they are first normalized into corresponding fields and values by creating a dedicated index pattern for the data source.</p><h3>KQL Overview</h3><p><strong>KQL (Kibana Query Language)</strong> is a search query language used to search the ingested logs/documents in the elasticsearch. Apart from the KQL language, Kibana also supports <strong>Lucene Query Language</strong>. We can disable the KQL query as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*n7zGpVdXM3WA6Abj.png" /></figure><p>In this task, we will be exploring KQL syntax. With KQL, we can search for the logs in two different ways.</p><ul><li>Free text search</li><li>Field-based search</li></ul><h4><strong>Free text Search</strong></h4><p>Free text search allows users to search for the logs based on the <strong>text-only</strong>. That means a simple search of the term security will return all the documents that contain this term, irrespective of the field.</p><p><strong>WILD CARD</strong></p><p>KQL allows the wild card * to match parts of the term/word. Let&#39;s find out how to use this wild card in the search query.</p><p><strong>Logical Operators (AND | OR | NOT)</strong></p><p>KQL also allows users to utilize the logical operators in the search query. Let us see the examples below.</p><p><strong>1- OR Operator</strong></p><p>We will use the <strong>OR</strong> operator to show logs that contain either the <strong>United States</strong> or <strong>England</strong>.</p><p><strong>Search Query:</strong> &quot;United States&quot; <strong>OR</strong> &quot;England&quot;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*YSkPJoqfJXkORTKj.png" /></figure><p><strong>2- AND Operator</strong></p><p>Here, we will use <strong>AND</strong> Operator to create a search that will return the logs that contain the terms “<strong>UNITED STATES</strong>” AND “<strong>Virginia</strong>.”</p><p><strong>Search Query: </strong>&quot;United States&quot; <strong>AND</strong> &quot;Virginia&quot;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*C-61JrezlMCU9Ov6.png" /></figure><p><strong>3- NOT Operator</strong></p><p>Similarly, we can use <strong>NOT</strong> Operator to remove the particular term from the search results. This search query will show the logs from <strong>the United States</strong>, including all states but ignoring Florida.</p><p><strong>Search Query:</strong> &quot;United States&quot; <strong>AND NOT</strong> (&quot;Florida&quot;)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0I-Qg4IyWmhsMEd0MzXVug.png" /></figure><h4><strong>Field-based search</strong></h4><p>In the Field-based search, we will provide the field name and the value we are looking for in the logs. This search has a special syntax as FIELD : VALUE. It uses a colon : as a separator between the field and the value. Let&#39;s look at a few examples.</p><p><strong>Search Query:</strong> <strong>Source_ip</strong> : 238.163.231.224 <strong>AND </strong>UserName<strong> </strong>: Suleman</p><p><strong>Explanation:</strong> We are telling Kibana to display all the documents in which the <strong>field</strong> Source_ip contains the value <strong>19.112.190.54</strong> and UserName as Suleman as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bs13tMz6EvVFTBEmPQFV6A.gif" /></figure><h3>Creating Visualizations</h3><p>The visualization tab allows us to visualize the data in different forms like Table, Pie charts, Bar charts, etc.</p><h4><strong>Create Visualization</strong></h4><p>There are a few ways to navigate to the visualization tab. One way is to click on any field in the discover tab and click on the visualization as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LzEeE-7JmHpk4zPE.gif" /></figure><p>We can create multiple visualizations by selecting options like tables, pie charts, etc.</p><h4><strong>Correlation Option</strong></h4><p>Often, we require creating correlations between multiple fields. Dragging the required field in the middle will create a correlation tab in the visualization tab. Here we selected the Source_Country as the second field to show a correlation among the client Source_IP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*XwDKlwoyQsxs3rZwQvpR1g.png" /></figure><p>We can also create a table to show the values of the selected fields as columns, as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*zEz__BOe9D20Jvzp_EbFEg.png" /></figure><p>The most important step in creating these visualizations is to save them. Click on the <strong>save Option</strong> on the right side and fill in the descriptive values below. We can add these visualizations to the already existing dashboard, or we can create a new one as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*dJKJrwklv0H3W_39thapQQ.png" /></figure><p>Steps to take after creating Visualizations:</p><ul><li>Create a visualization and Click on the Save button at the top right corner.</li><li>Add the title and description to the visualization.</li><li>We can add the visualization to any existing Dashboard or a new dashboard.</li><li>Click <strong>Save and add to the library</strong> when it’s done.</li></ul><h4><strong>Failed Connection Attempts</strong></h4><p>We will utilize the knowledge gained above to create a table to display the user and the IP address involved in failed attempts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*siUC2P0btQIOscYuZSafOQ.gif" /></figure><h3>Creating Dashboard</h3><p>Dashboards provide good visibility on the logs collection. A user can create multiple dashboards to fulfil a specific need.</p><p><strong>Creating Custom Dashboard</strong></p><p>By now, we have saved a few searches from the Discover tab and created some visualizations, and saved them. It’s time to explore the dashboard tab and create a custom dashboard. The steps to create a dashboard are:</p><ul><li>Go to the Dashboard tab and click on the <strong>Create dashboard.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*QohB64ukK16f4Vjl.png" /></figure><ul><li>Click on <strong>Add from Library.</strong></li><li>Click on the visualizations and saved searches. It will be added to the dashboard.</li><li>Once the items are added, adjust them accordingly, as shown below.</li><li>Don’t forget to save the dashboard after completing it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZmDgIkntoVe9bNPIrcTpHw.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44a9173e7cf4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to SIEM]]></title>
            <link>https://medium.com/@4ghora/introduction-to-siem-107d6a66e041?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/107d6a66e041</guid>
            <category><![CDATA[qradar]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[elastic]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Sun, 10 Mar 2024 10:17:55 GMT</pubDate>
            <atom:updated>2024-03-10T10:17:55.835Z</atom:updated>
            <content:encoded><![CDATA[<p>SIEM stands for <strong>Security Information and Event Management system</strong>. It is a tool that collects data from various endpoints/network devices across the network, stores them at a centralized place, and performs correlation on them. This room will cover the basic concepts required to understand SIEM and how it works.</p><h3>Network Visibility through SIEM</h3><p>We can divide our network log sources into two logical parts:</p><h4><strong>Host-Centric Log Sources</strong></h4><p>These are log sources that capture events that occurred within or related to the host. Some log sources that generate host-centric logs are Windows Event logs, Sysmon, Osquery, etc. Some examples of host-centric logs are:</p><ul><li>A user accessing a file</li><li>A user attempting to authenticate.</li><li>A process Execution Activity</li><li>A process adding/editing/deleting a registry key or value.</li><li>Powershell execution</li></ul><h4><strong>Network-Centric Log Sources</strong></h4><p>Network-related logs are generated when the hosts communicate with each other or access the internet to visit a website. Some network-based protocols are SSH, VPN, HTTP/s, FTP, etc. Examples of such events are:</p><ul><li>SSH connection</li><li>A file being accessed via FTP</li><li>Web traffic</li><li>A user accessing company’s resources through VPN.</li><li>Network file sharing Activity</li></ul><h4>Importance of SIEM</h4><p>As all these devices generate hundreds of events per second, examining the imglogs on each device one by one in case of any incident can be a tedious task. That is one of the advantages of having a SIEM solution in place. It not only takes logs from various sources in real-time but also provides the ability to correlate between events, search through the logs, investigate incidents and respond promptly. Some key features provided by SIEM are:</p><ul><li>Real-time log Ingestion</li><li>Alerting against abnormal activities</li><li>24/7 Monitoring and visibility</li><li>Protection against the latest threats through early detection</li><li>Data Insights and visualization</li><li>Ability to investigate past incidents.</li></ul><h3>Log Sources and Log Ingestion</h3><p>Every device in the network generates some kind of log whenever an activity is performed on it, like a user visiting a website, connecting to SSH, logging into his workstation, etc. Some common devices that are found in a network environment are:</p><h4>Windows Machine</h4><p>Windows records every event that can be viewed through the Event Viewer utility. It assigns a unique ID to each type of log activity, making it easy for the analyst to examine and keep track of. To view events in a Windows environment, type Event Viewer in the search bar, and it takes you to the tool where different logs are stored and can be viewed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nrk2w1q_c7qDxmTn5WqcFg.gif" /></figure><h4>Linux Workstation</h4><p>Linux OS stores all the related logs, such as events, errors, warnings, etc. Which are then ingested into SIEM for continuous monitoring. Some of the common locations where Linux store logs are:</p><ul><li><strong>/var/log/httpd</strong> : Contains HTTP Request / Response and error logs.</li><li><strong>/var/log/cron</strong> : Events related to cron jobs are stored in this location.</li><li><strong>/var/log/auth.log and /var/log/secure</strong> : Stores authentication related logs.</li><li><strong>/var/log/kern</strong> : This file stores kernel related events.</li></ul><p><strong>Here is a sample of a cron log:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*0-Ngqo9Vu46w7bBI81MHkQ.png" /></figure><h4>Web Server</h4><p>It is important to keep an eye on all the requests/responses coming in and out of the webserver for any potential web attack attempt. In Linux, common locations to write all apache related logs are <strong>/var/log/apache</strong> or <strong>/var/log/httpd.</strong></p><p><strong>Here is an example of Apache Logs:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*eDdpqg5fhL5S5Udf-t47sg.png" /></figure><h4>Log Ingestion</h4><p>All these logs provide a wealth of information and can help in identifying security issues. Each SIEM solution has its own way of ingesting the logs. Some common methods used by these SIEM solutions are explained below:</p><p><strong>1) Agent / Forwarder: </strong>These SIEM solutions provide a lightweight tool called an agent (forwarder by Splunk) that gets installed in the Endpoint. It is configured to capture all the important logs and send them to the SIEM server.</p><p><strong>2) Syslog: </strong>Syslog is a widely used protocol to collect data from various systems like web servers, databases, etc., are sent real-time data to the centralized destination.</p><p><strong>3) Manual Upload:</strong> Some SIEM solutions, like Splunk, ELK, etc., allow users to ingest offline data for quick analysis. Once the data is ingested, it is normalized and made available for analysis.</p><p><strong>4) Port-Forwarding:</strong> SIEM solutions can also be configured to listen on a certain port, and then the endpoints forward the data to the SIEM instance on the listening port.</p><p>An example of how Splunk provides various methods for log Ingestion is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8jjx1t6yDjuYNCC51Fh1HQ.png" /></figure><h3>WHY SIEM</h3><p>SIEM is used to provide correlation on the collected data to detect threats. Once a threat is detected, or a certain threshold is crossed, an alert is raised. This alert enables the analysts to take suitable actions based on the investigation.</p><h3>SIEM Capabilities</h3><p>SIEM is one major component of a Security Operations Center (SOC) ecosystem, as illustrated below. SIEM starts by collecting logs and examining if any event/flow has matched the condition set in the rule or crossed a certain threshold</p><p><strong>Some of the common capabilities of SIEM are:</strong></p><ul><li>Correlation between events from different log sources.</li><li>Provide visibility on both Host-centric and Network-centric activities.</li><li>Allow analysts to investigate the latest threats and timely responses.</li><li>Hunt for threats that are not detected by the rules in place.</li></ul><h4>SOC Analyst Responsibilities</h4><p>SOC Analysts utilize SIEM solutions in order to have better visibility of what is happening within the network. Some of their responsibilities include:</p><ul><li>Monitoring and Investigating.</li><li>Identifying False positives.</li><li>Tuning Rules which are causing the noise or False positives.</li><li>Reporting and Compliance.</li><li>Identifying blind spots in the network visibility and covering them.</li></ul><h3>Analysing Logs and Alerts</h3><p>SIEM tool gets all the security-related logs ingested through agents, port forwarding, etc. Once the logs are ingested, SIEM looks for unwanted behavior or suspicious pattern within the logs with the help of the conditions set in the rules by the analysts. If the condition is met, a rule gets triggered, and the incident is investigated.</p><h4>Dashboard</h4><p>Dashboards are the most important components of any SIEM. SIEM presents the data for analysis after being normalized and ingested. The summary of these analyses is presented in the form of actionable insights with the help of multiple dashboards.</p><p>Each SIEM solution comes with some default dashboards and provides an option for custom Dashboard creation. Some of the information that can be found in a dashboard are:</p><ul><li>Alert Highlights</li><li>System Notification</li><li>Health Alert</li><li>List of Failed Login Attempts</li><li>Events Ingested Count</li><li>Rules triggered</li><li>Top Domains Visited</li></ul><p>An example of a Default dashboard in Qradar SIEM is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*INq7P3NeZmqRcb4Byy97Bg.png" /></figure><h4>Correlation Rules</h4><p>Correlation rules play an important role in the timely detection of threats allowing analysts to take action on time. Correlation rules are pretty much logical expressions set to be triggered. A few examples of correlation rules are:</p><ul><li>If a User gets 5 failed Login Attempts in 10 seconds — Raise an alert for Multiple Failed Login Attempts</li><li>If login is successful after multiple failed login attempts — Raise an alert for Successful Login After multiple Login Attempts</li><li>A rule is set to alert every time a user plugs in a USB (Useful if USB is restricted as per the company policy)</li><li>If outbound traffic is &gt; 25 MB — Raise an alert to potential Data exfiltration Attempt (Usually, it depends on the company policy)</li></ul><p>How a correlation rule is created</p><p><strong>Use-Case 1:</strong></p><p>Adversaries tend to remove the logs during the post-exploitation phase to remove their tracks. A unique Event ID <strong>104</strong> is logged every time a user tries to remove or clear event logs. To create a rule based on this activity, we can set the condition as follows:</p><p><strong>Rule:</strong> If the Log source is WinEventLog <strong>AND </strong>EventID is <strong>104 </strong>— Trigger an alert Event Log Cleared</p><p><strong>Use-Case 2:</strong></p><p>Adversaries use commands like <strong>whoami </strong>after the exploitation/privilege escalation phase. The following Fields will be helpful to include in the rule.</p><ul><li>Log source: Identify the log source capturing the event logs</li><li>Event ID: which Event ID is associated with Process Execution activity? In this case, event id 4688 will be helpful.</li><li>NewProcessName: which process name will be helpful to include in the rule?</li></ul><p><strong>Rule:</strong> If Log Source is WinEventLog <strong>AND </strong>EventCode is <strong>4688, </strong>and NewProcessName contains <strong>whoami, </strong>then Trigger an ALERT WHOAMI command Execution DETECTED</p><h4>Alert Investigation</h4><p>When monitoring SIEM, analysts spend most of their time on dashboards as it displays various key details about the network in a very summarized way.</p><p>Once an alert is triggered, the events/flows associated with the alert are examined, and the rule is checked to see which conditions are met.</p><p>Based on the investigation, the analyst determines if it’s a True or False positive. Some of the actions that are performed after the analysis are:</p><ul><li>Alert is False Alarm. It may require tuning the rule to avoid similar False positives from occurring again.</li><li>Alert is True Positive. Perform further investigation.</li><li>Contact the asset owner to inquire about the activity.</li><li>Suspicious activity is confirmed. Isolate the infected host.</li><li>Block the suspicious IP.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=107d6a66e041" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wazuh]]></title>
            <link>https://medium.com/@4ghora/wazuh-740401d2b42c?source=rss-db2a6b8380f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/740401d2b42c</guid>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[defensive]]></category>
            <category><![CDATA[edr]]></category>
            <dc:creator><![CDATA[Aditya Yadav]]></dc:creator>
            <pubDate>Sat, 09 Mar 2024 21:23:31 GMT</pubDate>
            <atom:updated>2024-03-09T21:23:31.999Z</atom:updated>
            <content:encoded><![CDATA[<p>Endpoint detection and response (EDR) are a series of tools and applications that monitor devices for an activity that could indicate a threat or security breach. These tools and applications have features that include:</p><ul><li>Auditing a device for common vulnerabilities</li><li>Proactively monitoring a device for suspicious activity such as unauthorised logins, brute-force attacks or privilege escalations</li><li>Visualising complex data and events into neat and trendy graphs</li><li>Recording a device’s normal operating behaviour to help with detecting anomalies</li></ul><p>Created in 2015, <a href="https://wazuh.com/">Wazuh</a> is an open-source, freely available and extensive EDR solution.</p><h3>Wazuh Agents</h3><p>Devices that record the events and processes of a system are called agents.</p><p>Agents monitor the processes and events that take place on the device, such as authentication and user management.</p><p>Agents will offload these logs to a designated collector for processing, such as Wazuh.</p><p>Wazuh can guide you through the agent deployment process provided you fill out some pre-requisites such as:</p><ul><li>Operating System</li><li>The address of the Wazuh server that the agent should send logs to (this can be a DNS entry or an IP address)</li><li>What group the agent will be under — you can sort agents into groups within Wazuh if you wish</li></ul><p>This wizard can be launched by navigating to the following location on the Wazuh server: <strong>Wazuh -&gt; Agents -&gt; Deploy New Agent</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*moa6f6UlmLERfc3e.png" /></figure><h4><strong>Installing the Wazuh agent on Windows:</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*TyoHovrPJE0QRM66.png" /></figure><h4><strong>Installing the Wazuh agent on Debian/Ubuntu:</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*ApZhJJUxgD_ZXCiq.png" /></figure><h4>Wazuh Vulnerability Assessment &amp; Security Events</h4><p>Wazuh’s Vulnerability Assessment module is a powerful tool that can be used to periodically scan an agent’s operating system for installed applications and their version numbers.</p><p><strong>For example, the agent in the screenshot below has a version of Vim that is vulnerable to CVE-2019–12735.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*Bwb87EGU5_FI_u-3.png" /></figure><p>module will perform a full scan when the Wazuh agent is first installed on a device and <strong>must</strong> be configured to run at a set interval then after (by default, this is set to 5 minute intervals when enabled) like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/356/0*s2CTM9YzhjxOQzHA.png" /></figure><p>Wazuh is capable of testing an agent’s configuration against certain rulesets to check for compliance.</p><h3>Wazuh Policy Auditing</h3><p>Wazuh is capable of auditing and monitoring an agent’s configuration whilst proactively recording event logs.</p><p>When the Wazuh agent is installed, an audit is performed where a metric is given using multiple frameworks and legislations such as NIST, MITRE and GDPR.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*J3_NTxmkDOBRK3Vi.png" /><figcaption>For example, see how this agent DC-01 scores against MITRE, NIST, and SCA:</figcaption></figure><p>Wazuh presents a broad illustration of the logs.</p><h3>Monitoring Logons with Wazuh</h3><p>Wazuh’s security event monitor is capable to actively record both successful and unsuccessful authentication attempts.</p><p>Let’s look at this animated picture below as an example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8QjO5MJqVAZQbWAR.gif" /></figure><p>The alert was created because someone tried to log onto the agent “<strong>ip-10–10–73- 118</strong>” with the user “<strong>cmnatic</strong>” which does not exist. I have summarized this alert into the table below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9bojfCu07YBIrgtbU-ZgpA.png" /></figure><p>For reference, this alert is stored in a specific file on the Wazuh management server: /var/ossec/logs/alerts/alerts.log</p><p>Looking at the animated gif below, we can see how Wazuh has created an alert for successful login to a Window’s server running the Wazuh agent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kzBKGwFErd-DLVVn.gif" /></figure><p>The animated gif below shows the number of Windows agent events/alerts triggered to show how many times a user has logged on. . In this case, it narrows down the total logon events of <strong>285</strong> to <strong>79</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n-Bq9GADtCHeVzJq.gif" /></figure><p>Navigate to the “Management” tab by pressing <strong>Wazuh</strong> -&gt; <strong>Management </strong>and open the “Rules” module like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/0*eODwhJao1evlbxH1.png" /></figure><h3>Collecting Windows Logs with Wazuh</h3><p>All sorts of actions and events are captured and recorded on a Windows operating system like:</p><ul><li>authentication attempts</li><li>networking connections</li><li>files that were accessed</li><li>behaviours of applications and services.</li></ul><pre>This information is stored in the Windows event log using a tool called Sysmon. </pre><p>We can use the Wazuh agent to aggregate these events recorded by <em>Sysmon </em>for processing to the Wazuh manager.</p><p>Sysmon uses rules that are made in XML formatting to be triggered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3DEUnCnrZubwpWZxOLRj3w.png" /><figcaption>XML snippet above, we are telling Sysmon to monitor for the event of the powershell.exe process starting.</figcaption></figure><p>To instruct Sysmon to do, we need to execute the Sysmon application and provide the aforementioned configuration file like so: Sysmon64.exe -accepteula -i detect_powershell.xml</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*s2KIxVjCs8LrvsM0HAy94w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*JjVDogF6QlBIb44H7p9TqQ.png" /></figure><p>We can verify that Sysmon has accepted our configuration file by navigating to the Event Viewer and searching for the “<strong>Sysmon</strong>” module</p><p>Wazuh agent file location at: C:\Program Files (x86)\ossec-agent\ossec.conf</p><h3>Collecting Linux Logs with Wazuh</h3><p>Capturing logs from a Linux agent is a simple process similar to capturing events from a Windows agent. We will be using Wazuh’s log collector service to create an entry on the agent to instruct what logs should be sent to the Wazuh management server.</p><p>Wazuh comes with many rules that enable Wazuh to analyze log files and can be found in /var/ossec/ruleset/rules. Some common applications include:</p><ul><li>Docker</li><li>FTP</li><li>WordPress</li><li>SQL Server</li><li>MongoDB</li><li>Firewalld</li><li>And many, many more (approximately 900).</li></ul><p>However, you can always make your own rules. In this task, Wazuh will digest <em>Apache2</em> logs using the 0250-apache_rules.xml ruleset.</p><p>Wazuh management servers configuration file location in linux /var/ossec/etc/ossec.conf</p><h3>Auditing Commands on Linux with Wazuh</h3><p>Wazuh utilises the auditd package that can be installed on Wazuh agents running on Debian/Ubuntu and CentOS operating systems.</p><p>Auditd monitors the system for certain actions and events and will write this to a log file.</p><p>We can then use the log collector module on a Wazuh agent to read this log file and send it to the Wazuh management server for processing.</p><p>Auditd rules are located in the following directory: /etc/audit/rules.d/audit.rules. We will be adding our rules manually.</p><h3>Wazuh API</h3><p>The Wazuh management server features a rich and extensive API to allow the Wazuh management server to be interacted with using the command line. Because the Wazuh management server requires authentication, we must first authenticate our client.</p><h4><strong>Using Wazuh’s API Console</strong></h4><p>Wazuh has a powerful, integrated API console within the Wazuh website to query management servers and agents. Whilst it is not as extensive as using your own environment (where you can create and run scripts using python, for example), it is convenient.</p><p>To find this API console, we need to open the “Tools” category within the Wazuh heading at the top:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*7Tqs6crpFuvb-pgtJw6QCw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1maWzuCT9d7mhZyQevqDYg.gif" /></figure><h3>Generating Reports with Wazuh</h3><p>Wazuh features a reporting module that allows you to view a summarised breakdown of events that have occurred on an agent.</p><p>First, we will need to select a view to generate reports from. In this example, I want to generate a report of the security events in the last 24 hours. To do so, I will need to open the view: <strong>1. Modules -&gt; 2. Security Events</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*MwmtREoEhRNvRfvl.png" /></figure><p>Now, if there have been alerts within the last 24 hours, I can generate a report like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EvqOEth6m14GhWf_A_15BA.png" /></figure><p>First, press on the “<strong>Wazuh</strong>” heading at the top of the screen and select “<strong>Management</strong>”, and then click on the “<strong>Reporting</strong>” text located under the “<strong>Status and Reports</strong>” sub-heading:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*QY3G3s7JMjR8ju7B8R8dNw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*J5GYvkgvhElvUuLnsj4vAQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=740401d2b42c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>