The company page: Infrastructure & security
Open any company in the CRM and you'll find an Infrastructure & security group on the record. It's the day-to-day, single-screen read of the partner's environment — the same picture the Strategic Business Review turns into its three telemetry chapters, but live and always on, so you don't have to build a review to see whether a customer's backups ran last night.
The four clusters
The group is split into four clusters, each answering one question a technician or account manager actually asks:
- ＋Fleet — the devices under management: how many, their health, patch and OS compliance, warranty runway, and what's aging out.
- ＋Network — the connectivity and infrastructure picture: what's online, what's degraded, and anything flagged.
- ＋Security — endpoint protection coverage, open detections, phishing pressure, and identity hygiene.
- ＋Backup — protected workloads, recent backup success, and anything left unverified.
Where the numbers come from
The clusters are fed by your monitoring, security, and backup feeds — the read-only integrations you connect under Settings → Integrations. The record talks in themes, not vendors: it shows "your security posture" and "your backup picture," not the brand names of the tools behind them. That's the same principle the SBR follows, and it means changing a vendor doesn't change how the page reads.
Freshness stamps
Every cluster carries a freshness stamp — when its numbers were last read from the feed. That stamp is doing real work: a "protected" backup cluster that hasn't updated in a week is telling you something different than one read an hour ago. If a number looks surprising, check the stamp first — you may be looking at data that's waiting on the next pull, not a real change in the environment.
The open-alert strip
Above the clusters sits a strip of open alerts — the AI integration alerts that have fired for this company and haven't resolved yet. It's the "what needs attention right now" line: backups that have been failing for days, a critical detection sitting open, a phishing spike, a fleet slipping out of compliance. An empty strip means nothing has tripped a threshold. For exactly what each alert means and when it fires, see "Integration alerts: what fires and when."
When a cluster is empty: three states and their fixes
A cluster with no numbers tells you why, and each state has a clear next step — the same three states you'll see in the SBR's Data feeds panel:
| What it says | What it means | How to fix it |
|---|---|---|
| Not connected | The feed behind this cluster isn't set up for your workspace. | Connect the integration under Settings → Integrations. The cluster fills in on the next pull. |
| Connected but unmapped | The integration is on, but this company isn't matched to a company in it yet. | Map the company in that integration. Once matched, the cluster starts reading its data. |
| Mapped but no data | Everything's wired, but this company genuinely has nothing there — no assets, no detections, no backups reported. | Nothing to fix on the Current side; there's simply nothing to show for this customer yet. |
How it ties to the SBR
This group and the Strategic Business Review read the same feeds. The company record is the always-on operational view; the SBR is the quarterly, partner-facing telling of it — the three telemetry chapters (security posture, fleet & network health, backup & continuity). If a cluster here is empty because a feed is unmapped, that same feed will be greyed in the review's Data feeds panel until you map it. Fix it once, and both light up. See "Strategic Business Reviews: the QBR, rebuilt on evidence."