The Cybersecurity Extension for SAP serves as a direct alternative to Onapsis for SAP vulnerability management, threat detection, and custom code security. This guide outlines the essential steps for configuring SAP Solution Manager to support your transition from Onapsis, ensuring your platform is ready to host the Cybersecurity Extension for SAP.
Executive Summary
Switching from Onapsis to the Cybersecurity Extension for SAP requires a strategic transition of your SAP security infrastructure. Unlike Onapsis, which utilizes dedicated consoles and sensors, the Cybersecurity Extension for SAP is an addon developed by Layer Seven Security that integrates directly into your existing SAP Solution Manager. Because Solution Manager is the industry-standard platform for application lifecycle management—utilized by over 12,000 SAP customers—it provides a robust and familiar environment for managing your security landscape.
This transition involves preparing your Solution Manager environment to ensure seamless operation. By completing the mandatory configuration steps within Solution Manager, you establish the foundation necessary to replace your current Onapsis components. Once the transition is complete, you can decommission all Onapsis consoles, sensors, addons, and user accounts from your SAP systems. This guide focuses on the first phase of this preparation: verifying your basic configuration to ensure the system is ready for the new extension.
Key Takeaways
- The Cybersecurity Extension for SAP is an addon for SAP Solution Manager, not a standalone console.
- Solution Manager usage rights are included in standard SAP support, making it a cost-effective platform for security management.
- Transitioning allows you to remove all Onapsis consoles, sensors, and associated user accounts from your SAP landscape.
- Successful deployment requires the completion of all “Basic Configuration” steps within the SAP Solution Manager setup.
How do you prepare SAP Solution Manager for the transition?
The Cybersecurity Extension for SAP requires the successful completion of the Basic Configuration scenario within SAP Solution Manager. To begin, execute transaction SOLMAN_SETUP or navigate to the work center labeled “SAP Solution Manager Configuration – Configuration (All Scenarios).” From there, select “Basic Configuration” under “Cross Scenario Configuration – Mandatory Configuration.”
Ensure the status of every step in the Basic Configuration is marked green, indicating completion. If any steps are marked red or yellow, follow the provided guided procedures to resolve these items before proceeding with the extension installation.
What is the next step in the transition process?
After confirming that your basic configuration is complete and the status indicators are green, you must move on to the managed system configuration. This step ensures that the specific SAP systems you intend to monitor are correctly integrated with your Solution Manager environment.
Frequently Asked Questions
What happens to my Onapsis components after the switch?
Once you have successfully transitioned to the Cybersecurity Extension for SAP, you can remove all Onapsis consoles and sensors from your SAP landscape. Additionally, you should remove any Onapsis-specific users and addons that were previously required for the Onapsis solution to function.
Is the Cybersecurity Extension for SAP a standalone product?
No, it is not a standalone product. It is an addon designed specifically for SAP Solution Manager. This architecture leverages your existing investment in SAP’s application lifecycle management platform, which is already used by over 12,000 SAP customers worldwide for system monitoring and diagnostics.
Do I need to pay for additional platform licenses for Solution Manager?
No. Usage rights for SAP Solution Manager are typically included in your standard SAP support agreement. By using the Cybersecurity Extension for SAP, you are utilizing an existing platform rather than deploying and licensing a separate, third-party security console.