Layer Seven Security Brings SAP Cybersecurity Extension to BTP as Clean Core Strategy Expands

The Cybersecurity Extension for SAP from Layer Seven Security can now be deployed through SAP Build Work Zone on SAP Business Technology Platform Cloud Foundry.

The update reflects how the product is being aligned with clean-core architecture, SAP BTP-based extension models, and SAP Fiori-based user experience. Deploying the extension on BTP places those controls within the same extension and user experience layers used across modern SAP landscapes

Cybersecurity Extension Adds SAP BTP and Work Zone Deployment

Layer Seven Security’s Cybersecurity Extension for SAP is typically deployed through an embedded Fiori model within SAP systems. That model keeps frontend and backend components together, which simplifies lifecycle management and reduces dependencies.

The extension can now run through SAP Build Work Zone on SAP BTP Cloud Foundry, using a cloud extension model with Fiori applications delivered through SAP BTP rather than constrained by the backend system.

Setup requires a configured SAP BTP environment, including a subaccount, connectivity through SAP Cloud Connector, a backend destination, Cloud Foundry services, and a Work Zone subscription. The extension is deployed as a packaged application, with content imported into the launchpad and access managed through role assignments.

How SAP BTP and Fiori Shape Security Delivery

SAP BTP is positioned by SAP as the foundation for building, integrating, and extending applications across SAP and non-SAP environments. It supports development, integration, automation, and governance services that run outside core ERP systems.

The move suggests a clear alignment with that direction. SAP positions BTP as a platform for building, integrating, and extending applications outside core systems. Deploying the extension on BTP aligns with that model, placing controls in the same layer where applications and integrations are now managed.

That structure also shapes how those controls are accessed. SAP Fiori provides the role-based interface for interacting with applications and workflows through a centralized launchpad. Deploying the extension through SAP Build Work Zone keeps it within that interface while reducing dependency on backend system constraints.

In embedded models, frontend capabilities are tied to backend SAPUI5 versions, which can limit updates in older environments such as SAP ECC. SAP’s clean-core approach and BTP model separate those layers from the core system.

While clean core is usually discussed in terms of custom code and application extensions, the Cybersecurity Extension for SAP update shows the model extending to cybersecurity. Capabilities can be surfaced through BTP while still connecting to SAP data and processes.

Two Deployment Models for the Cybersecurity Extension

Layer Seven Security positions the Cybersecurity Extension for SAP as a single tool covering vulnerability management, threat detection, compliance monitoring, and custom code analysis across SAP environments. This approach promises consolidation, bringing multiple SAP security functions into one operational layer.

The extension can now be deployed in two ways. The established approach uses an embedded Fiori model, where frontend and backend components run in the same system and are managed within the core environment. The new approach uses SAP BTP, where the interface and application logic are delivered through SAP BTP while still connecting to SAP data and processes.

These deployment options reflect how SAP environments are being structured around platform and extension layers. As SAP customers move toward SAP S/4HANA, RISE with SAP, and SAP BTP, this extension shows how security capabilities can follow. Controls are delivered across platform and interface layers, where applications are extended and where users interact with them.

What This Means for SAPinsiders

• Security moves into application workflows. Delivering controls through SAP Fiori-based interfaces places detection and response closer to how users work. This shifts security from a backend activity to one embedded in operational workflows and decision points.
• SAP BTP becomes a platform layer for security delivery. Placing the extension on SAP BTP aligns security with the same platform used for applications and integrations. That positions SAP BTP as a coordination point where data, access, and security intersect.
• Extension models standardize how security is delivered. Deploying the extension on SAP BTP mirrors how SAP applications are being extended outside the core system. This creates a more consistent delivery model where security follows the same architectural patterns as other enterprise functionality.