<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Network on SolCyber Knowledgebase</title><link>https://kb.solcyber.com/supported-data-sources-categories/network/</link><description>Recent content in Network on SolCyber Knowledgebase</description><generator>Hugo</generator><language>en</language><atom:link href="https://kb.solcyber.com/supported-data-sources-categories/network/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Firewall</title><link>https://kb.solcyber.com/supported-data-sources-categories/network/azure-firewall/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kb.solcyber.com/supported-data-sources-categories/network/azure-firewall/</guid><description>&lt;h2 id="create-an-azure-event-hub-namespace-and-event-hub"&gt;&lt;strong&gt;Create an Azure Event Hub Namespace and Event Hub&lt;/strong&gt;&lt;a class="anchor" href="#create-an-azure-event-hub-namespace-and-event-hub"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Azure Portal&lt;/strong&gt;: Navigate to the Azure Portal.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Create a Namespace&lt;/strong&gt;: Search for &amp;ldquo;Event Hubs&amp;rdquo; and create a new Event Hub namespace.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Create an Event Hub&lt;/strong&gt;: Within the namespace, create an Event Hub (e.g., &amp;ldquo;firewall-logs&amp;rdquo;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="configure-azure-firewall-to-send-logs-to-event-hub"&gt;&lt;strong&gt;Configure Azure Firewall to Send Logs to Event Hub&lt;/strong&gt;&lt;a class="anchor" href="#configure-azure-firewall-to-send-logs-to-event-hub"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Azure Firewall Policy&lt;/strong&gt;: Go to the Azure Firewall policy associated with your firewall.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Diagnostic Settings&lt;/strong&gt;: Under &amp;ldquo;Diagnostics&amp;rdquo;, create a new diagnostic setting.&lt;/p&gt;</description></item><item><title>Cisco ASA</title><link>https://kb.solcyber.com/supported-data-sources-categories/network/cisco-asa/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kb.solcyber.com/supported-data-sources-categories/network/cisco-asa/</guid><description>&lt;blockquote class='book-hint note' &gt;&lt;div class="kb-alert-icon" aria-hidden="true"&gt;&lt;svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round"&gt;&lt;circle cx="12" cy="12" r="10"/&gt;&lt;path d="M12 16v-4"/&gt;&lt;path d="M12 8h.01"/&gt;&lt;/svg&gt;&lt;/div&gt;&lt;div class="kb-alert-body"&gt;
&lt;p&gt;&lt;strong&gt;NOTE: Be sure to make a backup of your current ASA configuration before performing any changes.&lt;/strong&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/blockquote&gt;
&lt;h2 id="configure-logging-using-the-asdm-gui"&gt;Configure logging using the ASDM GUI&lt;a class="anchor" href="#configure-logging-using-the-asdm-gui"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Ensure logging is enabled. Visit &lt;strong&gt;Configuration &amp;gt; Features &amp;gt; Properties &amp;gt; Logging &amp;gt; Logging Setup&lt;/strong&gt;. Check the &lt;strong&gt;Enable logging&lt;/strong&gt; check box in order to enable syslog output.&lt;/li&gt;
&lt;/ul&gt;
&lt;figure&gt;&lt;img src="https://www.cisco.com/c/dam/en/us/support/docs/security/pix-500-series-security-appliances/63884-config-asa-00-00.png" alt=""&gt;&lt;figcaption&gt;&lt;/figcaption&gt;&lt;/figure&gt;
&lt;ul&gt;
&lt;li&gt;Configure the external Syslog Server: Choose &lt;strong&gt;Syslog Servers&lt;/strong&gt; under Logging and click &lt;strong&gt;Add&lt;/strong&gt; in order to add a syslog server. Enter the &lt;strong&gt;IP of your Remote Ingestion Node (RIN)&lt;/strong&gt;, choose &lt;strong&gt;UDP&lt;/strong&gt;, and enter &lt;strong&gt;1514 (or another port if instructed by SolCyber)&lt;/strong&gt; in the Add Syslog Server box and choose &lt;strong&gt;OK&lt;/strong&gt; when you are done. Be sure to leave &amp;ldquo;Log messages in Cisco EMBLEM format&amp;rdquo; unchecked.&lt;/li&gt;
&lt;/ul&gt;
&lt;figure&gt;&lt;img src="https://www.cisco.com/c/dam/en/us/support/docs/security/pix-500-series-security-appliances/63884-config-asa-00-01.png" alt=""&gt;&lt;figcaption&gt;&lt;/figcaption&gt;&lt;/figure&gt;
&lt;ul&gt;
&lt;li&gt;Enable Log Sending: choose &lt;strong&gt;Logging Filters&lt;/strong&gt; in the logging section. This presents you with each possible logging destination and the current level of logs that are sent to those destinations. Choose Syslog Servers and click &lt;strong&gt;Edit&lt;/strong&gt;. &lt;/li&gt;
&lt;/ul&gt;
&lt;figure&gt;&lt;img src="https://www.cisco.com/c/dam/en/us/support/docs/security/pix-500-series-security-appliances/63884-config-asa-00-06.png" alt=""&gt;&lt;figcaption&gt;&lt;/figcaption&gt;&lt;/figure&gt;
&lt;ul&gt;
&lt;li&gt;Select &lt;strong&gt;Filter on Severity&lt;/strong&gt; and &lt;strong&gt;Informational&lt;/strong&gt;. Click OK.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Apply&lt;/strong&gt; - this will apply the new settings. If you experience any issues with connectivity after applying the new config, revert to your backup config.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="configure-logging-using-the-cli"&gt;Configure Logging Using the CLI&lt;a class="anchor" href="#configure-logging-using-the-cli"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;div class="kb-code" data-lang="text"&gt;
 &lt;div class="kb-code-head"&gt;
 &lt;span class="kb-code-lang"&gt;text&lt;/span&gt;&lt;/div&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#e6edf3;background-color:#0d1117;-moz-tab-size:2;-o-tab-size:2;tab-size:2;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;logging enable
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;logging host &amp;lt;interface_name&amp;gt; &amp;lt;sensor_ip&amp;gt; udp
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;logging permit-hostdown
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;logging timestamp
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;logging device-id hostname
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;no logging emblem&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;The &amp;lt;interface_name&amp;gt; argument specifies the interface through which you access your Remote Ingestion Node (RIN). The sensor_ip argument specifies the IP address of the RIN.&lt;/p&gt;</description></item><item><title>SonicWall Firewall</title><link>https://kb.solcyber.com/supported-data-sources-categories/network/sonicwall-firewall/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kb.solcyber.com/supported-data-sources-categories/network/sonicwall-firewall/</guid><description>&lt;blockquote class='book-hint warning' &gt;&lt;div class="kb-alert-icon" aria-hidden="true"&gt;&lt;svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round"&gt;&lt;path d="M10.29 3.86 1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z"/&gt;&lt;path d="M12 9v4"/&gt;&lt;path d="M12 17h.01"/&gt;&lt;/svg&gt;&lt;/div&gt;&lt;div class="kb-alert-body"&gt;
&lt;p&gt;&lt;strong&gt;Pre-requisites:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt; Must have GMS server or On-Prem Analytics server installed and configured.&lt;/li&gt;
&lt;li&gt;Have an Address Object Created on the Firewall for SonicWall Analytics system.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;/blockquote&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Navigate to &lt;strong&gt;Device &amp;gt; Log &amp;gt; Syslog&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select &lt;strong&gt;Syslog Servers&lt;/strong&gt; and Click &lt;strong&gt;Add&lt;/strong&gt;&lt;/p&gt;
&lt;figure&gt;&lt;img src="https://sonicwall.rightanswers.com/portal/app/portlets/results/onsitehypermedia/090210909738018.png?linkToken=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJpYXQiOjE3NDE3MDg3ODksImV4cCI6MTc3MzI0NDc4OX0.OOycVRsZRZ414MC21NZIxQm7FHwaI__DvMripkeY-j8" alt=""&gt;&lt;figcaption&gt;&lt;/figcaption&gt;&lt;/figure&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select the Name or IP address of the Syslog server from the dropdown. Enter the port provided by SolCyber.&lt;/p&gt;</description></item><item><title>Cisco Meraki Firewall Syslog</title><link>https://kb.solcyber.com/supported-data-sources-categories/network/cisco-meraki-firewall-syslog/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kb.solcyber.com/supported-data-sources-categories/network/cisco-meraki-firewall-syslog/</guid><description>&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Go to &lt;strong&gt;Network-wide&lt;/strong&gt; &amp;gt; &lt;strong&gt;Configure&lt;/strong&gt; &amp;gt; &lt;strong&gt;General&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click &lt;strong&gt;Add a syslog server&lt;/strong&gt; to define a new server. &lt;/p&gt;
&lt;p&gt;&lt;img src="https://documentation-be.securonix.com/bundle/securonix-cloud-user-guide/page/content/resources/images/imported/cisco%5c_meraki/1.png?%5c_LANG=enus" alt="" /&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Server IP&lt;/strong&gt;: The Securonix Hub IP address.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Port:&lt;/strong&gt; generally, we will use udp port &lt;strong&gt;1514&lt;/strong&gt;. The SolCyber team may specify another port to use if 1514 is already in use on the Hub. &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Roles:&lt;/strong&gt; The roles to send to the server.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Choose the type of events to export:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Event Log&lt;/strong&gt;: The messages from the dashboard under Monitor &amp;gt; Event Log.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Flows&lt;/strong&gt;: Inbound and outbound traffic flow-generated syslog messages that include the source, destination, and port numbers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;URL:&lt;/strong&gt; HTTP GET requests generating syslog entries.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;</description></item></channel></rss>