Skip to main content

The EmberSecurity area

The EmberSecurity area in EmberCORE is where everything EmberSecurity sees on your boxes is read, sorted, and acted on. A tenant user sees only their own tenant. Fireball staff see every tenant and pick one from the scope menu at the top.

Who sees what​

Role in the tenantWhat they can do
Engineer and above, or an AuditorRead every view
AdminAlso acknowledge, assign, and close alerts, set maintenance windows, and set the plant location
Fireball staffSee every tenant, plus the central health banner

The views​

Command​

The first question: is anything wrong, and where. It counts alerts by severity over the last hour, day, or week, and shows how many boxes are reporting and how many have been silent for more than 15 minutes. Below that are the most serious live alerts, a heat strip with one cell per box (quiet, alerting, critical, or silent), and a chart of alerts per hour. A Live switch keeps it updating.

Fireball staff also see a banner here when EmberSecurity's central side needs attention, so an alert list that may be out of date is never mistaken for a calm plant.

Alert queue​

Each row shows the severity, title, box, source, state, and when it was raised. Filter by severity, by source (network watch, runtime, file integrity), by state, by time window up to 30 days, or by words in the alert. Open a row for the event's own details and its timeline.

OT activity​

What your PLCs are being told. Protocols are counted per box, and the view shows who talks to which PLC, a log of every PLC write, and an inventory of the devices EmberSecurity has seen. The inventory is learned from traffic, and nothing is scanned. Each device is marked New or Known, and each write is marked as inside or outside a maintenance window.

Plant network map​

A map of one box's devices drawn by Purdue level, from what EmberSecurity heard on that box in the last 24 hours. Devices first seen in that time are marked, and a write outside the maintenance window draws a red line you can follow to the alert.

Threat map​

A world map of outside addresses that tripped the network watch, and of the destinations Plasma stopped a box from reaching, with the top countries and the latest drops. It draws arcs from your plant's location, which a tenant Admin sets in Maintenance windows.

Blocked traffic​

What Plasma refused: packets blocked by destination, port, and protocol, with the time of the last drop and how many boxes are reporting. This view is read only.

Boxes​

Pick a box to see its four EmberSecurity containers, whether each is running, and when it last reported, then that box's alerts from the last 7 days and its file changes.

Posture​

A box's hardening checks, with a score and the checks that failed, once a box has completed a hardening run. A box that has not run one says so.

Maintenance windows​

The weekly times when PLC writes are expected, set per tenant by an Admin. With none set, every write counts as outside a window. The plant location lives here too.

Work an alert​

  1. Open the alert. Read the title and severity, then the box and source.
  2. Decide what it is. An unfamiliar device on a PLC leg is a question for whoever installed equipment this week. A PLC write outside the maintenance window is worth a call to the plant. A shell in a container nobody opened is worth treating as real until someone explains it.
  3. Acknowledge it, so the team knows someone has seen it.
  4. Assign it to the person who will follow up, by email.
  5. Close it with a note. The note is required. Say what it was and what was done, because the note is what the next person reads.

Acknowledging, assigning, and closing are recorded with who did them and when, and they appear in the audit trail.

When a view is empty​

An empty queue only means good news while the boxes are reporting, so the queue offers a link to check them. If no box has reported, the views say so instead of drawing an empty chart. If EmberSecurity cannot be reached, the view shows an error and not an empty table.

Next steps​