SpamAssassin VS Wazuh

spamassassin or rspamd or ASSP. All very good. Spamassassin just works, but you need to feed it a good cohort of spam and ham (about 1000 messages each). Most people only send it the spam which will then bias it quite a bit and not have it classify spam as spam unless it's the worst of the bunch. Spamassassin is a filter for your mail server. rspamd is the same idea. ASSP is highly configurable and a proxy.

https://spamassassin.apache.org/ ?

I'm currently looking into using a Bayesian spam filter like Bogofilter or Apache Spamassassin to help out. I'd run the contents of my Contact Us form through the filter after the initial validation, and if the contents are below my spam threshold, I would actually send out the contact us request.

Avoid it. Apache's SpameAssassin flags several TLDs including .xyz as 'suspicious' nTLD[1].

[1]: https://github.com/apache/spamassassin/blob/trunk/rulesrc/sa...

The famous spam filter SpamAssassin. Score: -0.6. A score below -5 is considered spam. -0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid This rule is automatically applied if your email contains a DKIM signature but other positive rules will also be added if your DKIM signature is valid. See immediately below. 0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Great! Your signature is valid 0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain Great! Your signature is valid and it's coming from your domain name 0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.001 HTML_MESSAGE HTML included in message No worry, that's expected if you send HTML emails 0.001 RCVD_IN_MSPIKE_H2 Average reputation (+2) 23.83.209.151 listed in wl.mailspike.net -0.001 SPF_HELO_NONE SPF: HELO does not publish an SPF Record 0.001 SPF_PASS SPF: sender matches SPF record Great! Your SPF is valid -0.01 T_KAM_HTML_FONT_INVALID Test for Invalidly Named or Formatted Colors in HTML -0.644 URIBL_SBL Contains an URL listed in the SBL blocklist -0.1 URIBL_SBL_A Contains URL\'s A record listed in the SBL blocklist

Maybe you updated spamassassin in the process? Because it looks like they have a list of "spammy TLDs" and .site is in it.

To detect whether incoming emails are malicious, mail servers also use spam scanners, such as Apache's popular SpamAssasin. The internal workings of these spam scanners can be somewhat complicated (involving Naive Bayes Classifiers on trained, large datasets, for the curious), but the primary takeaway is that these classification systems typically assign a numerical point value to an incoming email to determine the validity of the message. The higher the score, the more likely that the email is spam. For reference, the ISP Optimum states the following regarding their spam filtering:

There is currently no feature for excluding specific SCA rules however this feature has been requested here and would be added to the roadmap for future releases.

I use Wazuh instead. Greenbone CE is severely limited and requires payment for anything beyond the very basic. Super simple installation more features.

Seems like something that should be documented somewhere more official than a random reddit post for sure. Added it to https://github.com/wazuh/wazuh/issues/1112 for good measure.

Hmm, I've really been wanting to try Wazuh but since all our endpoints (Win10/11) are running a German locale I've run into https://github.com/wazuh/wazuh/issues/16842 when checking the compliance checks (CIS benchmarks) on a test installation of 4.6.

Monitoring & Active Measures - Exporting firewall events to an external time-series database like I describe above is good to see who is touching your firewall or accessing your web site. Using an Intrusion Detection System / Intrusion Prevention System (IDS/IPS) such as open-source Suricata, which is a free package on pfSense, and deploying file system integrity monitoring, such as the open-source Wazuh on the exposed server are also good approaches to protecting yourself.

We are actively working on enhancing the system to allow users to mark vulnerabilities as "not vulnerable" or hide them. You can track the progress of this enhancement on the following GitHub issue: (Enhancement - Mark Vulnerabilities as Not Vulnerable).

Hello, thanks for using Wazuh, I will try to answer your questions: 1- I am going to check with the team in charge to see if there is a way. 2- Untriaged is a default value that is placed on vulnerabilities that do not have low, medium or high values https://github.com/wazuh/wazuh/issues/12675 3- As in the previous point, the providers of vulnerability lists have not provided the data.

Agents getting frequently pending and disconnecting