Repository navigation
WatchLattice 0.8.0
Added
- Browser extension watchdog (
BrowserExtensionWatchdogmodule, on by
default): every five minutes it inventories the extensions in every Edge,
Chrome and Firefox profile of every user on the PC (from each profile's
Preferences,Secure Preferencesandextensions.json), and the
policies and registry entries that install extensions from outside the
browser (ExtensionInstallForcelist,ExtensionSettings, Firefox
Extensions\Install, and theSoftware\...\Extensionsregistrations
other programs write). The first check records a baseline; after that each
extension added is a warning naming its ID, name, version, browser, profile
and user, how it was installed (store, policy, another program, unpacked)
and whether by policy, and each policy added is a warning too. Removals,
new profiles and deleted profiles are Info. Read-only; it never disables or
removes an extension. New Event IDs 10001 to 10015. See its
README. (#39) - Approve as baseline on the dashboard's Alerts tab: select an
Autostart entry added or changed alert (or the verification alert that
follows it) and approve the entry exactly as it is now, so it raises no
alert when it comes back with that value, for example after an app removed
and re-added its Run value, or a task flipped back to a known setting. Any
other value still alerts. For a New browser extension alert it adds the
extension's ID toIgnoredExtensionIds. Approvals are stored in the hub's
appsettings.json(newPersistence:ApprovedEntries, one
sha256:<hash> <source>/<entry>line each), so approving goes through the
administrator prompt and the settings editor, keeps a settings backup and
restarts the hub; approved alerts are marked acknowledged, and an approval
is revoked by removing its line in Settings.ENTRY_ADDEDand
ENTRY_CHANGEDmessages now end with aFingerprint: sha256:<hash>line
for this. Event IDs are unchanged and approving raises no new events. See
approving entries.
(#40) - Script host audit (
ScriptHostAuditmodule, off by default): reads
Security log event 4688 every 30 seconds and reports launches of
PowerShell, mshta, wscript, cscript, rundll32, regsvr32, certutil,
bitsadmin and similar programs, with the parent program, user, elevation,
command line and why it was reported. A launch is a warning when an Office
app, a browser, a PDF reader or another script host started it, when its
command line uses an encoded PowerShell command, a hidden window, a
download,Invoke-Expression,javascript:or a known abuse of the
program (such ascertutil -urlcacheorregsvr32 scrobj.dll), or when a
Windows program runs from outside the Windows folder; critical when a
suspicious parent combines with another reason. Ordinary launches are not
reported unlessMinimumSeverityisInfo. It only works when Windows
process creation auditing is already on, and never turns it on: when it is
off the dashboard shows one informational alert saying so, with the
auditpolcommand in the README. Known-good launches are allowed with
AllowedLauncheswildcard rules or with Approve as baseline (new
ScriptHostAudit:ApprovedLaunches, the exact parent, program and command
line). A cleared or overwritten Security log is reported. Read-only; it
never blocks or stops a process. New Event IDs 11001 to 11009. See its
README. (#41) - What to check by hand on Windows now has the
0.8.0 checks: upgrading the 0.7.0 MSI, then the browser extension
watchdog, approving entries as baseline and the script host audit.
Changed
- Upgrading from 0.7.0: run the 0.8.0 MSI over an MSI install, or use
Install update in the tray on either kind of install. Your
appsettings.jsonis kept; the browser extension watchdog starts on its
own (its first check records a baseline and raises nothing else), and the
script host audit stays off until you turn it on. Existing baselines and
alert history are unchanged.
What's Changed
- Add a browser extension watchdog module by @notbrianbob in #39
- Approve startup entries and browser extensions as baseline from the dashboard by @notbrianbob in #40
- Add a script host audit module (off by default) by @notbrianbob in #41
- Prepare v0.8.0: changelog section and Windows hand checks by @notbrianbob in #42
Full Changelog: v0.7.0...v0.8.0