However I can see when any IPv6 begins with 2a02:12xx:: then it’s Swisscom (biggest swiss ISP). But I can’t remember any of their hundreds of IPv4 prefixes.

ExtensibleMarkupLanguageHypertextTransferProtocolRequest

For services I host I really like this EULA:

If the Provider of the Service (the “Provider”) needs a place to crash and you have a sofa available, you should maybe give the Provider a break and let him sleep on your couch.

If you are caught in a dire situation wherein you only have enough time to save one person out of a group, and the Provider is a member of that group, you must save the Provider.

THE ACCESS IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO BLAH BLAH BLAH ISN’T IT FUNNY HOW UPPER-CASE MAKES IT SOUND LIKE THE LICENSE IS ANGRY AND SHOUTING AT YOU.

Edit: original found here: https://github.com/pirate/security-growler

I would recommemd setting up greylog. It’s pipelines are really mighty and not that hard to learn. You can run it in a VM.

If you really want to you can run filebeat on windows with a file output, so it will write everything in json format to a file. However you will still have to parse ot, make it searchable etc.

https://m.xkcd.com/583/

https://ittavern.com/troubleshooting-asking-the-right-questions/

If you are running a version of Exchange Server earlier than the Aug 2022 SU, We send you thoughts and prayers, and very strong but gentle guidance to update your servers to the latest SU immediately.

https://techcommunity.microsoft.com/t5/exchange-team-blog/coming-soon-enabling-extended-protection-on-exchange-server-by/ba-p/3911849

Originally was:

“DVWA v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at blind\source\high.php.”

Source report: https://github.com/KLSEHB/vulnerability-report/blob/c1f3f27286e435d1bd5893a5fea2ffbe9fb55cbd/Dvwa_vulnerability