pfsense:suricata:install_suricata
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pfsense:suricata:install_suricata [2021/01/15 13:03] – peter | pfsense:suricata:install_suricata [2021/01/22 13:59] (current) – [PFSense - Suricata - Install Suricata] peter | ||
---|---|---|---|
Line 5: | Line 5: | ||
- [[PFSense: | - [[PFSense: | ||
- [[PFSense: | - [[PFSense: | ||
+ | - [[PFSense: | ||
+ | - [[PFSense: | ||
+ | - [[PFSense: | ||
---- | ---- | ||
- | |||
- | ===== Have Suricata Monitor the WAN Interface ===== | ||
- | |||
- | Navigate to **Services -> Suricata -> Interfaces**. | ||
- | |||
- | Click **Add**. | ||
- | |||
- | In **General Settings**: | ||
- | |||
- | * Enable: | ||
- | * Interface: | ||
- | * Description: | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | In **Logging Settings**: | ||
- | |||
- | * Send Alerts to System Log: **Not Checked**. | ||
- | * Enable Stats Collection: | ||
- | * Enable HTTP Log: **Checked**. | ||
- | * Append HTTP Log: **Checked**. | ||
- | * Log Extended HTTP Info: **Checked**. | ||
- | * Enable TLS Log: **Not Checked**. | ||
- | * Enable File-Store: | ||
- | * Enable Packet Log: **Not Checked**. | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | In **EVE Output Settings**: | ||
- | |||
- | * EVE JSON Log: **Not Checked**. | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | In **Alert and Block Settings**: | ||
- | |||
- | * Block Offenders: | ||
- | * IPS Mode: **Legacy Mode**. | ||
- | * Kill States: | ||
- | * Which IP to Block: | ||
- | * Block On DROP Only: **Not Checked**. | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | In **Performance and Detection Engine Settings**: | ||
- | |||
- | * Run Mode: **AutoFP**. | ||
- | * Max Pending Packets: | ||
- | * Detect-Engine Profile: | ||
- | * Pattern Matcher Algorithm: | ||
- | * Signature Group Header MPM Context: | ||
- | * Inspection Recursion Limit: | ||
- | * Delayed Detect: | ||
- | * Promiscuous Mode: **Checked**. | ||
- | * Interface PCAP Snaplen: | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | In **Networks Suricata Should Inspect and Protect**: | ||
- | |||
- | * Home Net: **default**: | ||
- | * External Net: **default**. | ||
- | * Pass List: **default**. | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | In **Alert Suppression and Filtering**: | ||
- | |||
- | * Alert Suppression and Filtering: | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | In **Arguments here will be automatically inserted into the Suricata configuration**: | ||
- | |||
- | * Advanced Configuration Pass-Through: | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | ===== Set Categories for the WAN Interface to Monitor ===== | ||
- | |||
- | Click on **WAN Categories**. | ||
- | |||
- | In **Select the rulesets (Categories) Suricata will load at startup**: | ||
- | |||
- | * Within each Ruleset, click the checkbox against whichever rules to enable. | ||
- | * Ruleset: ET Open Rules: | ||
- | * emerging-attack_response.rules | ||
- | * emerging-botcc.portgrouped.rules | ||
- | * emerging-botcc.rules | ||
- | * emerging-ciarmy.rules | ||
- | * emerging-coinminer.rules | ||
- | * emerging-compromised.rules | ||
- | * emerging-current_events.rules | ||
- | * emerging-dos.rules | ||
- | * emerging-dshield.rules | ||
- | * emerging-exploit.rules | ||
- | * emerging-malware.rules | ||
- | * emerging-mobile_malware.rules | ||
- | * emerging-phishing.rules | ||
- | * emerging-scan.rules | ||
- | * emerging-worm.rules | ||
- | * Ruleset: Snort Text Rules: | ||
- | * snort_attack-responses.rules | ||
- | * snort_backdoor.rules | ||
- | * snort_bad-traffic.rules | ||
- | * snort_blacklist.rules | ||
- | * snort_botnet-cnc.rules | ||
- | * snort_ddos.rules | ||
- | * snort_dos.rules | ||
- | * snort_exploit-kit.rules | ||
- | * snort_exploit.rules | ||
- | * snort_malware-backdoor.rules | ||
- | * snort_malware-cnc.rules | ||
- | * snort_malware-other.rules | ||
- | * snort_malware-tools.rules | ||
- | * snort_phishing-spam.rules | ||
- | * snort_policy-spam.rules | ||
- | * snort_scan.rules | ||
- | * snort_specific-threats.rules | ||
- | * snort_spyware-put.rules | ||
- | * snort_virus.rules | ||
- | * snort_web-attacks.rules | ||
- | |||
- | ---- | ||
- | |||
- | |||
- | ===== Create Lists ===== | ||
- | |||
- | |||
- | ==== Created a Pass List ==== | ||
- | |||
- | Navigate to **Services -> Suricata -> Pass List**. | ||
- | |||
- | <WRAP alert> | ||
- | **ALERT: | ||
- | |||
- | Realistically, | ||
- | |||
- | In that situation, a passlist makes sense. | ||
- | |||
- | For about any other case, it does not. | ||
- | |||
- | Use custom PASS rules instead if you really need passlist functionality. | ||
- | |||
- | </ | ||
- | |||
- | |||
- | ---- | ||
==== Created a suppress list ==== | ==== Created a suppress list ==== |
pfsense/suricata/install_suricata.1610715806.txt.gz · Last modified: 2021/01/15 13:03 by peter