Release notes
November 2026
Standards
- SOC 2. Choose SOC 2 for clients whose own customers ask for a SOC 2 report. 97 checks map to eight of the Security criteria (logical access, outside threats, data leaving, malware, vulnerabilities, and monitoring), so a client's results become ongoing evidence for their auditor. Trimtab doesn't decide whether a client passes SOC 2; the auditor does. See SOC 2.
Bridge
- Security fixes from an internal penetration test. Signing out now ends the session on the server, so a copied cookie stops working, and no session lasts more than 24 hours. Failed sign-ins are slowed down per account as well as per address. Every Bridge page sends a Content Security Policy. Alert destinations can't point at Azure's internal platform address or IPv6 forms of an IPv4 address. Invite links always use Trimtab's own address. Everyone was signed out once when this shipped.
- Access review. Owners can download everyone who can get into their organization, with role, client access, sign-in method, last sign-in, and what to check, then record the review in the activity log. Auditors for SOC 2, HIPAA, and CMMC ask for exactly this. See Access review.
- Activity log. A full record of sign-ins, failed sign-in attempts, and changes in your organization, with the IP address each came from, under Settings > Activity log. Filter it by dates, person, or kind of activity, search it, and export it to a spreadsheet. Entries are kept for a year. See Activity log.
- Sign-in in steps. The sign-in page now asks for your email first, then your password, then your authenticator code, one at a time.
- Sign in with Microsoft. Owners can let their team use work Microsoft accounts in place of passwords (Settings > Team > Microsoft sign-in), and each person switches on their new Account page. You still enter your Trimtab authenticator code, accounts are matched by Microsoft's IDs rather than email, and at least one owner keeps a password. See Signing in with Microsoft.
- Safer Microsoft 365 connections. Connecting a tenant is now a Microsoft sign-in that only an admin of that tenant can finish, and Trimtab takes the tenant from Microsoft's answer to that sign-in. A tenant already connected to another Trimtab organization can't be connected again until it's disconnected there.
- Trimtab staff can't let themselves in. Harbor Master can invite only an organization's first owner; after that, only the organization's owners invite people. A sign-in reset for a locked-out owner is emailed to that owner's own address, never shown to Trimtab staff, and the organization's other owners are told.
- Saved alert secrets are locked with Azure Key Vault. The key that encrypts saved PSA passwords, API keys, and webhook secrets is now itself encrypted by a Key Vault key that can't be copied out, so a copy of the server's disk or a backup can't open them. Sign-ins use a separate key. Everyone is signed out once when this ships.
- Saved PSA secrets stay with their address. If you change where an alert destination sends (a PSA's URL or site, the Autotask API username, or a webhook URL), enter its secrets again. Trimtab never sends a saved secret to a new address.
- Trimtab checks its own access. A new Microsoft 365 check (M365-026) fails if Trimtab's app in a tenant has more than read-only access: an Entra role that can make changes (directly or through a group), an API permission Trimtab doesn't ask for, an Exchange role, or a secret or certificate someone added to it in the tenant. It also fails on roles Trimtab's app is eligible for in Privileged Identity Management, delegated permissions beyond signing in, apps it owns, and any Azure role, and it warns when it can't read one of these (usually Exchange, before Global Reader is assigned). It uses the permissions Trimtab already has, so there's nothing to reconnect. See Keep Trimtab read-only.
Lookout 0.6.5
- Re-enrolling proves it's the same device. When Lookout is installed again with an enrollment key, it sends its current credential so the Bridge keeps the device and its history.
- Bridge: an enrollment key plus a device's name and serial number no longer takes over that device. Without the device's current credential, the Bridge enrolls a new device and notes it in the activity log, so a leaked key can't cut off a real device and report in its place. See Re-enrolling a device.
October 2026
Standards
- Five more standards: NIST Cybersecurity Framework 2.0, PCI DSS v4.0.1, NYDFS Part 500, SEC Regulation S-P, and a cyber insurance readiness profile (the controls carriers commonly ask about on applications). Choose them per client on the Clients page; every existing check is mapped to them. PCI DSS descriptions are Trimtab's summaries, because the standard's text is copyrighted.
- HIPAA: HHS's proposed 2025 Security Rule update (required MFA, encryption, and more) has not been finalized, so Trimtab continues to map to the rule in force. The HIPAA page notes the proposal.
- Three new standards: CMMC Level 1, CIS Controls v8.1 Implementation Group 1, and the FTC Safeguards Rule. Choose them per client on the Clients page. Every existing check is mapped to them.
- Five new checks: antivirus scans run regularly (AV-005), automatic updates are on (PAT-004), legacy TLS and SSL are turned off (HRD-010), device is centrally managed (MGT-001), and the Exchange malware filter blocks risky attachment types (EXO-009).
Bridge
- Alerts. Hear about new failures, fixes, and devices that stop reporting by email (as it happens or as a daily summary), in Microsoft Teams or Slack, through a signed webhook, or as tickets in ConnectWise PSA, Autotask, or HaloPSA. Each failing check gets one ticket, with fix steps, and Trimtab closes it when the check passes again. See Alerts.
- Settings. Team, Alerts, Lookout updates, and Support access now live under one Settings item in the top bar. Alerts has a switch for each channel (email, Teams, Slack, webhook, and PSA tickets); turn one on and its settings open below it.
- CMMC system security plan and POA&M. Each CMMC Level 2 client has a system security plan covering all 110 requirements, with an SPRS score estimate, a POA&M that follows the 32 CFR 170.21 rules for conditional status, and printable, branded documents. Trimtab's checks show as evidence and suggest a status and a draft statement. See System security plan and POA&M.
- Policies and staff sign-off. Each client has a policy library, started from eight plain-English templates. Publish versions, then email staff a personal link to read and acknowledge each one; Trimtab records who acknowledged which version and when, with reminders and a printable record. Staff can be imported from Microsoft 365. See Policies and staff sign-off.
- Reconnect reminders. When a release needs a Microsoft 365 permission a tenant hasn't approved, Owners and Admins see a banner, and the tenant shows a Reconnect button on the Clients page.
- Intune checks. Seven checks for Intune-managed Windows, Mac, iPhone, and Android devices: compliance policies for every platform in use, devices without a policy counting as not compliant, overall compliance, encryption, policies that require a passcode and encryption, app protection on phones, and regular check-ins. They count as evidence for CMMC's mobile device requirements (AC.L2-3.1.18 and 3.1.19) in the system security plan. They need three new read-only permissions, so reconnect Microsoft 365 for each client. See Connect Microsoft 365.
- 10 more Microsoft 365 checks, for 49 in all: phishing-resistant MFA for admins, just-in-time Global Administrators (PIM), emergency access accounts, blocking device code sign-in, short admin sessions, a custom banned password list, SharePoint sharing limited to approved domains, external calendar detail, outbound spam notifications, and zero-hour auto purge. Still no new permissions.
- 16 more Microsoft 365 checks, for 39 in all: cloud-only admin accounts, risky sign-in and risky user policies, managed-device sign-in, text and voice codes, admin consent requests, tenant creation, stale guests, SharePoint legacy authentication, guest resharing, OneDrive sync, Safe Links and Safe Attachments, mail flow rules and allow lists that skip spam filtering, External tags, shared mailbox sign-in, and Outlook add-ins. They use the permissions Trimtab already has, so there's nothing to reconnect. See Microsoft 365 checks.
- Report branding and spreadsheet export. Put your company name, logo, accent color, and contact details (email, phone, website) on reports under Settings > Report branding; reports say who prepared them and for which client. Export to spreadsheet on Fleet downloads every check as a CSV file for Excel. See Reports.
- Accepted exceptions. Accept the risk of a failing check with a reason, an approver, and an expiry date. Accepted findings stop counting against the score, sending alerts, and appearing in the fix script, and reports list them under Accepted by the client. Review them under Checks > Accepted exceptions. See Accepted exceptions.
- Per-client alerts. Select Alerts on a client to turn channels on or off for that client, set its own severity, and add the client's own contacts, who get email about that client only. See Different settings for one client.
- Autotask setup lists. Select Connect and load lists to choose the queue, issue and sub-issue type, priorities, and closed status from your own Autotask, and search companies by name instead of typing IDs. Trimtab suggests a company for each client whose name matches. See Autotask.
- Locked-out owners. If an organization's only owner loses their authenticator, Trimtab support can create a one-time sign-in reset link for them after confirming who they are. See Manage people.
- Edit your team. Owners can change a person's first name, last name, and email from Manage on the Team page. Changing the email changes how that person signs in. New people enter their first and last name when they accept an invite.
- Trimtab support access. Owners and admins can let Trimtab support into their organization for 24 hours, 3 days, or 7 days, at View only or Technician level, and turn it off at any time. Support sessions show a banner on every page, and everything support does is in the activity log. See Trimtab support access.
-
Organizations. Each MSP or direct customer is its own organization with its own database, so no organization can see another's clients, devices, or findings. Device credentials, enrollment keys, and invites only reach the organization that issued them. New organizations are invite-only. See Security and privacy.
-
Team and invites. Owners invite people with a one-time link and choose a role (Owner, Admin, Technician, Viewer) and access to all or selected clients. Invitees set their own password and authenticator. Includes sign-in resets, disabling accounts, and an activity log.
- Standards per client. Choose CMMC Level 2, HIPAA, or both when you add a client, and change them any time. Scores, findings, reports, and the Checks page follow the client's standards.
- Redesigned device and tenant pages. Findings by severity with a side panel, a category strip, and Needs attention, Passing, Controls, and Logbook tabs.
- Fix script. A PowerShell script that applies the settings the Windows checks look for, on any edition including Home. Download it from a device page with that device's failing checks filled in. It previews by default, keeps risky changes opt-in, and starts a rescan when it's done. See Fix script.
- Correct course. Every finding has step-by-step Take the helm instructions. Hand us the helm (automated fixes) is coming soon.
- Plain English. Every requirement shows what it means in everyday words, its official text, and a source link.
- Fleet refresh. The Fleet page refreshes every minute, and Rescan tenants re-runs every Microsoft 365 scan.
- Last scan and Overdue. The Fleet shows when each device was last scanned and flags devices that haven't reported for 3 or more days.
Microsoft 365
- Three new checks, for findings cyber insurance scans commonly raise: idle Microsoft 365 web sessions sign out (M365-012), SPF is published for custom domains (EXO-010), and anti-phishing protection is on (EXO-011). With Defender for Office 365, EXO-011 also checks that impersonation protection is on. No new permissions are needed; the SPF check uses public DNS.
- Secure Score tab. Each tenant page shows its Microsoft Secure Score with 90 days of history, a category breakdown, and every recommended action, largest gain first, with Microsoft's fix steps. Actions that need a license the tenant doesn't have (for example Defender for Office 365) are listed separately. Track each action's status, owner, and notes in Trimtab. No new permissions are needed; the connection stays read-only.
- Microsoft 365 connection with 11 identity, admin, application, sharing, and Secure Score checks.
- Exchange Online checks (8): mailbox auditing, the unified audit log, external forwarding, modern authentication, SMTP AUTH, DKIM, and DMARC.
Lookout 0.6.4
- After installing an update, Lookout checks in right away with its new version and runs a fresh scan, so the Bridge shows the new version and findings within minutes instead of up to an hour later (starting with the update after this one).
- Bridge: commands in Take the helm steps have a copy button.
Lookout 0.6.3
- Windows Home and Pro. Lookout reports each device's Windows edition. On Windows Home, the BitLocker, LAPS, and central management findings explain why Home can't meet them and what to do instead (Device encryption, or an upgrade to Pro).
- Credential Guard (HRD-008) is a warning rather than a failure on Home and Pro, which can't run it.
- Take the helm steps now cover Windows Home and single devices where they only offered Group Policy or Intune, including password complexity, the logon banner, USB storage, process auditing, and automatic updates.
Lookout 0.6.2
- Shows the Trimtab icon next to Trimtab Lookout in Settings → Apps and Programs and Features.
Lookout 0.6.1
- Listed in Settings → Apps and Programs and Features as Trimtab Lookout, with its version, publisher, and an Uninstall button. RMM software inventories pick it up too.
- Uninstalling on the device now tells the Bridge, so the device moves to Removed instead of going quiet.
- The Bridge's Fleet page shows each device's Lookout version and flags devices behind the current release.
Lookout 0.6.0
- Remove from the Bridge. Select Remove Lookout on a device page; Lookout uninstalls itself at its next check-in and the device moves to Removed.
- Automatic, signed updates. Lookout checks in hourly and installs newer releases that carry a valid Trimtab signature. Owners can switch to manual updates under Settings > Lookout updates.
- Update older devices to 0.6.0 once by hand; from then on they keep themselves current.
Lookout 0.5.0
- Adds checks AV-005, PAT-004, HRD-010, and MGT-001. Install it over 0.4.0; the device keeps its registration.
Lookout 0.4.0
- Renamed to Trimtab Lookout. Scheduled tasks are now Trimtab Lookout Scan and Trimtab Lookout Upload. Upgrading replaces the previous tasks and keeps the device's registration.
- New hourly upload task delivers results queued while a device was offline.
- Results include step-by-step remediation for local reports.