Switching from Security Bridge to the Cybersecurity Extension for SAP requires verifying your SAP Solution Manager configuration. Because the Cybersecurity Extension for SAP operates as an addon for SAP Solution Manager, ensuring your managed system configuration is complete is the critical first step in transitioning your vulnerability management and threat detection.
Executive Summary
Transitioning from Security Bridge to the Cybersecurity Extension for SAP involves migrating your SAP vulnerability management, threat detection, and custom code security to a platform native to SAP Solution Manager. Unlike Security Bridge, the Cybersecurity Extension for SAP leverages existing Solution Manager infrastructure, which is included in standard SAP support and currently used by over 12,000 customers for application lifecycle management. This guide focuses on the technical prerequisite of ensuring your managed systems are correctly configured within Solution Manager. Once the transition is complete, you can safely decommission Security Bridge consoles, sensors, users, and addons from your SAP landscape. The following steps ensure your environment is prepared for a successful migration.
Key Takeaways
- The Cybersecurity Extension for SAP is an addon for SAP Solution Manager, not a standalone platform.
- Managed System Configuration must be completed for every target system before migrating.
- Standard SAP Solution Manager usage rights are included in SAP support.
- You can remove Security Bridge components only after the full transition is complete.
How do you verify Managed System Configuration?
To verify your configuration, execute transaction SOLMAN_SETUP or navigate to the “Configuration (All Scenarios)” work center in SAP Solution Manager. Once there, select “Managed System Configuration” under “Cross Scenario Configuration.” Highlight your target system in the “Technical Systems” tab and select “Configure System – Full Configuration.” Ensure the status of all steps is green (completed); if any steps are red or yellow, follow the provided guided procedures to resolve them.
Which configuration steps are optional?
During the “Finalize Configuration” phase, several activities are not required for the Cybersecurity Extension for SAP. You do not need to perform the following:
| Activity | Status Requirement |
|---|---|
| Setup Single Sign-On | Not required |
| Activate E2E Trace Upload Service | Not required |
| Introscope Host Adaptor | Not required |
| Apply Settings for EWA Monitoring | Not required |
| Byte Code Adaptor Installation (Java Systems) | Not required |
| Enable Remote R/3 Connection | Not required |
Note: The status of “Maintain Users,” “Finalize Configuration,” and “Check Configuration” may remain yellow.
FAQ
What is the primary difference between Security Bridge and the Cybersecurity Extension for SAP?
The Cybersecurity Extension for SAP is an addon for SAP Solution Manager, whereas Security Bridge is a separate platform. This allows users to manage security directly within their existing SAP application lifecycle management environment.
When can I remove Security Bridge from my systems?
You should only remove Security Bridge consoles, sensors, users, and addons after you have fully transitioned to the Cybersecurity Extension for SAP and confirmed the new solution is operating correctly.
Do I need extra licenses to use the Cybersecurity Extension for SAP?
The Cybersecurity Extension for SAP utilizes SAP Solution Manager, for which usage rights are already included in standard SAP support.