Reference
Provider, resource, and session fields
Reference the identity, activity, timing, capability, destination, and environment fields used by observed records.
Last reviewed September 12, 2026
Provider fields
Provider fields include name, description or enrichment state, official website when available, loading type, resource impact, first and last seen, activity status, known services, competitors, inventory, load relationships, and past-incident context. Dates and status reflect SiteWall’s project observations.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Field definitions | Review field definitions in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
| States | Read the workflow state with its timestamps, affected entity, and owner action. Acknowledging or closing a record changes review status; it does not remove the underlying observation or prove remediation. |
Apply the reference
- 1.
Open a representative source record
Use the project selector to choose the website you intend to review, then open Providers in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Read the field with its context
Interpret the value with its entity type, project, observation window, state, and source link. Do not compare values collected under materially different conditions as if they were equivalent.
- 3.
Carry the definition into the workflow
Use the field to navigate or prioritize, then make the operational decision in the provider, resource, session, finding, policy, or evidence workflow that owns it.
Resource fields
Resource fields cover URL and identity, provider, category, size, version or source context, first and last observation, security score and findings, load and execution timing, browser APIs and globals, network requests and destinations, code-analysis context, status, and policy state where available.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Identity | Confirm the URL or domain, provider association, first and last observation, and the project in which the entity was recorded. Open the linked detail record; a display name or enrichment label is not proof of ownership or approval. |
| Performance | Compare like-for-like sessions and treat captured timing as context, not a complete causal proof. |
| Access | Review browser APIs, globals, storage, and network destinations associated with the resource. Compare observed access with its documented purpose and representative journeys before deriving or restricting permissions. |
| Score | Use the value to prioritize review, then inspect the contributing findings and runtime evidence. A score or severity is a triage signal, not an approval decision or a confirmed incident. |
| Status fields | Read the state together with its timestamps and owner action; a workflow state does not erase the original observation. |
Apply the reference
- 1.
Open a representative source record
Use the project selector to choose the website you intend to review, then open Inventory in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Read the field with its context
Interpret the value with its entity type, project, observation window, state, and source link. Do not compare values collected under materially different conditions as if they were equivalent.
- 3.
Carry the definition into the workflow
Use the field to navigate or prioritize, then make the operational decision in the provider, resource, session, finding, policy, or evidence workflow that owns it.
Session fields
Session fields include session identifier and time, monitored page, browser and operating environment, user-agent details, resource activity, response and execution timing, errors, API use, network requests and status, globals, event listeners, and consent decisions when captured.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Context | Review context in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
| Timing | Compare like-for-like sessions and treat captured timing as context, not a complete causal proof. |
| Environment | Open a representative session and record its page, time, browser context, and observed resources. Use it to establish that the behavior occurred in that captured journey, not that it occurred for every visitor. |
| Status fields | Read the state together with its timestamps and owner action; a workflow state does not erase the original observation. |
Apply the reference
- 1.
Open a representative source record
Use the project selector to choose the website you intend to review, then open Sessions in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Read the field with its context
Interpret the value with its entity type, project, observation window, state, and source link. Do not compare values collected under materially different conditions as if they were equivalent.
- 3.
Carry the definition into the workflow
Use the field to navigate or prioritize, then make the operational decision in the provider, resource, session, finding, policy, or evidence workflow that owns it.