https://github.com/tester1010101/inboundpopup
:mag_right: Windows Defender Firewall Scanner to find "Inbound" rules. If a rule is found, an alert/pop-up is immediately sent to the user for further analysis. No downloads required! :saxophone:
https://github.com/tester1010101/inboundpopup
inbound popup real rule scanner time
Last synced: about 1 year ago
JSON representation
:mag_right: Windows Defender Firewall Scanner to find "Inbound" rules. If a rule is found, an alert/pop-up is immediately sent to the user for further analysis. No downloads required! :saxophone:
- Host: GitHub
- URL: https://github.com/tester1010101/inboundpopup
- Owner: tester1010101
- Created: 2022-01-06T18:06:05.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2022-12-28T21:09:09.000Z (over 3 years ago)
- Last Synced: 2025-05-19T00:16:35.246Z (about 1 year ago)
- Topics: inbound, popup, real, rule, scanner, time
- Language: PowerShell
- Homepage:
- Size: 8.79 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# InboundPopup :bell: :headphones:
* :loudspeaker: Scan Windows Firewall Rules to find "Inbound" rules.
* :musical_note: If an "inbound" rule is found, an alert/pop-up is sent to the user.
* :microphone: Best used in scenarios for Group Policy login/out scripts or with the Task Scheduler.
* :saxophone: Task Scheduler: On Event (Microsoft-Windows-Windows Firewall With Advanced Security/Firewall/2004-2005-2006)
# Pictures #
 
* 2004 - A rule has been added to the Windows Defender Firewall exception list.
* 2005 - A rule has been modified in the Windows Defender Firewall exception list.
* 2006 - A rule has been deleted in the Windows Defender Firewall exception list.
* If any of these events happens, the above script can be used to send the user a pop-up.
* Requires no external programs and the pop-up can pop instantly when a change is made.
* I added the batch script to make it work under "Task Scheduler", thanks to [Stack Overflow](https://stackoverflow.com/questions/665014/my-script-wont-run-under-the-task-scheduler-why).
* Edit the .batch_script to run the \Path\Popup.ps1 then you can add it (run.bat) in Task Scheduler.
* Anytime a rule is found in the inbound section, you'll get a pop-up to verify it, if it's ok, don't make any changes to it.
* Message me for any question/features that you may want me to add-in!
# Instructions ::
1) Place the Popup.ps1 script somewhere you can access & copy the path.
2) Right-click on "run-ps-startup.bat", Edit.
* Use the path you copied earlier.
* Paste the path to Popup.ps1 inside the batch file
* (replace the line after -File) ""%SYSTEMROOT%\System32\GroupPolicy\User\Scripts\Logon\Popup.ps1""
3) Schedule a task OR a login/out job for the Policy & test the magic!
# Purpose
* I kept getting inbound rules added/modified silently in the background and found that annoying. Here's a simple, no download, fix to it. *You can copy/paste the code if that's more convenient.*