--- title: "Security posture" canonical: "https://support.appfire.com/space/RM/3543073577/Security%20posture" format: markdown --- Use **Security posture** to understand how effectively risks are being managed across the domains of your enabled compliance frameworks. You can review risk trends, compare domain health over time, and drill down from frameworks to domains, controls, and their associated risks. Open LiveRisk in your Jira space, then click the **Security posture **tab. ## Before you begin - The** Security posture** tab requires the **Manage LiveRisk Risk Register** permission. The **LiveRisk Manager** and **LiveRisk Analyst** roles have this permission by default. - If no frameworks are available, ask a space administrator to enable them from **Space settings** > **Apps** > **Appfire LiveRisk** > **Controls**. See **[Controls](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459121502)**. ## Navigate Security posture Security posture organizes risk information in three levels: **Framework → Domain → Control** ![Appfire LiveRisk, the Security posture tab.](media://de93e181-4798-45a1-9c8a-31a7a72a13d2) Start by selecting a framework. You can then drill down into its domains and controls: - **Framework**: Shows coverage and risk information across the framework. Select a framework to view its domains. - **Domain**: Groups related controls within the framework. Select a domain to view its controls. - **Control**: Select a control to view the risks linked to it. Use the breadcrumb or back button to move back through the hierarchy. Use the date range at the top of the page to choose the period included in the charts and scores. Select a preset period or enter a start and end date. ![Appfire LiveRisk, Security posture tab with each section highlighted.](media://a2b71f94-7793-418d-a691-c494d2e66e2d) ## 1. Framework and domain information Framework and domain cards summarize the risk and control information available at each level. Depending on the level and available data, cards can show: - **Controls covered** - **Risks tracked** - **Mean risk score** - The number of **Domains** - The current risk tier Controls without associated risk data are shown as **Not tracked**. Use this information alongside the charts to identify areas with risk data and areas where coverage is limited. ### Investigate a domain Select a framework to view its domains. Each domain shows information about its control coverage and associated risks. You can click a domain to view the controls it contains. ![Appfire LiveRisk, domain investigation.](media://11713b32-ba60-4d0c-9962-5b477c3bd3e9) The **Aggregate risk score** chart updates to show the risk trend for the selected domain while the **Health graph** continues to provide domain-level context. ### Investigate a control Select a domain to view its controls. Control cards show whether a control is tracked and, where applicable, information about its associated risks, such as: - The number of linked risks - Mean risk score - Current risk tier - Risk status or treatment information Select a control to view the risks linked to it. ![Appfire LiveRisk, control investigation.](media://c9145a42-4e7f-455f-96e6-b0ffd0ebe39f) Selecting a control doesn’t change the meaning of the **Health graph**. The radar remains a domain-level visualization: each axis continues to represent an entire domain rather than an individual control. ## 2. Aggregate risk score The **Aggregate risk score** chart shows how risk scores change over the selected date range. The dashed **Risk appetite** line shows the risk-appetite threshold configured for the space. Use **Max** or **Mean** to change how the risk score trend is calculated. **Max** is selected by default. ## 3. Health graph When you select a framework, the **Health graph** compares the health of its domains. Each axis of the radar chart represents a **domain in the selected framework**. Individual controls and risks are not represented as separate axes. The graph measures health, so **farther outward is better**: - **100%** represents the healthiest end of the scale. - **0%** represents the least healthy end of the scale. - A larger overall radar shape generally indicates better security posture. The graph compares two points in time: - **Start of period**: Domain health at the beginning of the selected date range. - **Today**: Current domain health. This comparison helps you identify domains whose security posture has improved or worsened during the selected period. Hover over a domain to review the values behind its position on the chart. ### How health is calculated LiveRisk calculates health from the risk scores mapped to each domain. For the **Health graph**, LiveRisk applies the maximum score from the risk score trend to mapped risks and converts it to a health percentage: - A risk score of **1** corresponds to **100% health**. - A risk score of **8** corresponds to **0% health**. - Unscored risks are treated as having a score of **8** for the health calculation. As the calculated risk score decreases, domain health increases and its point moves outward on the radar chart. If a domain does not have enough risk data to calculate health, it is shown as untracked. An untracked domain should not be interpreted as having perfect health. ## How to interpret Security posture When reviewing Security posture, remember: - **Outward means healthier.** The radar measures security health rather than raw risk. - **Each axis represents a framework domain.** Controls and risks contribute to domain health but are not separate axes. - **Start of period and Today show change over time.** Compare them to see whether domain health has improved or worsened. - **Lower risk means better health.** As the calculated risk score decreases, domain health moves outward. - **Unscored risks count against health.** They are treated as score 8 in the health calculation. - **Untracked is not the same as healthy.** A domain without enough risk data should not be interpreted as having 100% health. - **Max and Mean change the risk trend view.** They do not change what the radar axes represent.