UpdateSet Logo
UpdateSet Loom logo

LOOM

IT service and security operations

One admin for incidents, changes, configuration, knowledge, vulnerabilities, security incidents, and threat indicators. Fifteen Payload plugins. No public portal.

Loom workspace

Foundational records

ITSM, security operations, MITRE, the configuration database, and knowledge share the same people, companies, and places.

  • Companies are customers, vendors, or manufacturers. Locations run from region and site down to a room.
  • A person is tied to a company, a location, a department, and a manager. Department is a field on the user, not its own table.
  • Groups and access grants decide who can create and edit. The same rules wrap every module.
Loom companies, locations, and user profiles

IT service management

Incidents, problems, and changes, each with child tasks, in one admin.

  • Any signed-in person can read them. Creating and editing needs an access grant. Only a super admin can delete.
  • Incidents move from New through Closed. Impact and urgency set a read-only priority. Problems hold cause, workaround, and fix notes.
  • Changes are Normal, Standard, or Emergency. The change and incident forms do not include an approvals panel.
Loom incidents, problems, and changes

Security incidents

A security case, separate from an ITSM incident.

  • State moves one step at a time from Draft through Closed. A skipped step is rejected.
  • The case can name a configuration item, an affected user, a vulnerability, knowledge articles, and threat indicators.
  • When MITRE is installed, a suggested countermeasure can open a task for a technique.
Loom security incident

Vulnerability response

The finding, the configuration item it sits on, and the task that groups the work.

  • A vulnerability stores the CVE, severity, a score, and whether an exploit exists.
  • A vulnerable item is one finding on one configuration item. Closing a remediation task does not close those items.
  • Findings can be imported as text. There is no scanner-import button.
Loom vulnerabilities and vulnerable items

Threat intelligence

Indicators are reference data. The response stays on the security incident.

  • An indicator needs a title, a type, and a value. Types include IP, domain, URL, hash, and email.
  • TLP:RED is never published on the TAXII server. A super admin can run a configured feed.
  • Security incidents list the indicators that apply.
Loom threat indicators

MITRE ATT&CK and D3FEND

Reference catalogs and navigator pages. These are not tickets.

  • ATT&CK covers tactics through detection strategies. D3FEND covers tactics, techniques, and artifacts.
  • Navigator pages switch between matrix and table. A super admin can import or export a Navigator layer.
  • The offline catalog loads in the admin. A download from MITRE stays off unless the deployment turns it on.
Loom ATT&CK navigator

CMDB and Axonius

The systems and services the other modules name. One configuration item, many records pointing at it.

  • Configuration items cover servers, applications, databases, and licenses. Service instances are application or business services.
  • An incident, problem, change, vulnerable item, or security incident can name that same configuration item.
  • Axonius can match a device, user, vulnerability, or software id to a Loom record. Live sync stays off until the deployment enables it.
Loom configuration items

Knowledge

Libraries and articles that staff attach to the work.

  • An article moves through Draft, Review, Published, and Retired. Published text stays locked until it returns to Draft.
  • Only a published article can be attached to an incident, problem, change, or security incident.
  • Staff read articles in the admin. There is no public portal.
Loom knowledge article

Relationships

A Relationship tab shows how a saved record connects to the rest of the workspace.

  • The picture is Hierarchical, Force, or By collection. Open a linked record, or remove the line.
  • Links follow companies, configuration items, incidents, knowledge, vulnerabilities, security incidents, threat indicators, and Axonius assets. Each line has a direction and a type.
  • CI links such as Runs on also live on the configuration item. The graph does not auto-draw group membership, who opened a ticket, or MITRE catalog rows. A security record can still mark a link as ATT&CK or D3FEND.
Loom relationship graph

Workflow and field suggestions

Record events can leave for n8n. Selected fields can suggest a value from the description.

  • A workflow posts record-created or State-changed events for incidents, problems, changes, security incidents, and vulnerable items. The flow runs in n8n. Loom does not change the record.
  • Auto decide can suggest category, impact, assignment, configuration item, and company. Problems omit category. Changes add type and risk.
  • There is no flow designer and no triage board in the admin.
Loom workflow runs and field suggestions

Staff sign in to the admin. Password sign-in can be hidden. Microsoft and Keycloak appear only when that provider is configured, and Loom matches the account by issuer and subject, not by email. API keys for the MCP server named Loom are created in the admin. Callers do not get a submission page or a storefront.

SEE LOOM AGAINST YOUR PROCESSES

Tell us how your service desk and security teams work today. We will map that work onto incidents, changes, the configuration database, and the security records Loom already keeps.

hello@updateset.com

Argus, UpdateSet’s MCP gateway, is a separate product. Read about Argus.