SAP Fiori Launchpad is the central web entry point for SAP applications, presenting tiles, pages, search, and user services in one interface. Security depends on the backend role model that feeds it, so the launchpad is best understood as an access surface rather than a simple homepage.
Expanded Definition
Fiori launchpad is the authenticated presentation layer for SAP access, but in security terms it behaves as an entitlement broker: the tiles, search results, and spaces a user sees are determined by backend authorizations, catalog assignments, and service exposure. That makes it materially different from a generic portal homepage. The term is often used loosely across SAP teams, yet its security meaning is narrower and more consequential. A launchpad can look benign while still exposing powerful transactions, OData services, or workflow actions if the underlying role model is overbroad. For governance purposes, treat it as an access surface that reflects identity decisions rather than a stand-alone application. This interpretation aligns with broader control thinking in NIST SP 800-53 Rev 5 Security and Privacy Controls and with NHI governance principles documented in Ultimate Guide to NHIs. The most common misapplication is treating the launchpad as a cosmetic front end, which occurs when security reviews ignore the role objects and technical services behind each tile.
Examples and Use Cases
Implementing Fiori Launchpad rigorously often introduces role-design friction, requiring organisations to weigh user simplicity against the risk of exposing too much business capability.
- A finance user sees a payments tile only because a backend role grants the related catalog and service permissions, not because the tile itself is secure.
- An automated service account authenticates through SAP integration and launches backend actions indirectly, which makes launchpad visibility relevant to NHI governance rather than only human IAM.
- A developer adds a new app to a page without reviewing the linked authorizations, creating a mismatch between interface access and transaction authority.
- Security teams review launchpad content alongside Ultimate Guide to NHIs to identify service accounts, API keys, and technical users that can reach sensitive SAP functions.
- Control owners map launchpad exposure to NIST SP 800-53 Rev 5 Security and Privacy Controls when validating least privilege and access review evidence.
Why It Matters in NHI Security
Fiori Launchpad matters because it hides privilege in plain sight. A user or service may appear to have harmless portal access while actually inheriting deep SAP capabilities through role chains, technical catalogs, or background integrations. That is especially important in NHI environments where non-human identities often accumulate excess privilege. NHIMG research shows that Ultimate Guide to NHIs reports 97% of NHIs carry excessive privileges, which makes front-end access reviews insufficient on their own. Practitioners should therefore examine the launchpad as evidence of underlying identity posture, not as proof of least privilege. The relevant governance question is not only “who can log in,” but “what backend authority is reachable from this interface, and by which human or machine identity.” That distinction also maps to NIST SP 800-53 Rev 5 Security and Privacy Controls for access enforcement and review. Organisations typically encounter launchpad risk only after a privileged transaction, data exposure, or automation failure has already occurred, at which point the term becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and OWASP Agentic AI Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207) and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-01 | Launchpad exposure reflects whether NHI access paths are overprivileged or poorly governed. |
| NIST CSF 2.0 | PR.AC-4 | Launchpad access depends on authorization enforcement and least-privilege assignment. |
| NIST Zero Trust (SP 800-207) | Launchpad should not be trusted as a safe boundary; access must be continuously evaluated. | |
| NIST SP 800-63 | AAL2 | Authenticated access to a launchpad relies on identity assurance for the session entry point. |
| OWASP Agentic AI Top 10 | LLM-04 | When agents act through SAP entry points, hidden tool access can amplify launchpad risk. |
Map launchpad roles to least privilege and verify access reviews cover both human and non-human identities.
Related resources from NHI Mgmt Group
- How should security teams govern SAP Fiori Launchpad access in role-based environments?
- How should SAP teams govern Fiori access without relying on the front end alone?
- Why can SAP Fiori create a false sense of least privilege?
- What should identity teams check when SAP Fiori is used on mobile and desktop?
