Firefighter Implementation Strategy

[Former Member]

Hello All,

We are implementing Firefighter in our landscape, and we want that all changes in SAP system should be done with Firefighter, but to reduce the usage of Firefighter we would be using our existing normal users for Daily Checks and monitoring without any change.

To do this, we need role/s which can be used for executing most of the Basis transactions with DISPLAY access only.

Appreciate if you can share such roles OR recommend whats the best strategy for implementing Firefighter.

Regards

Davinder

[Former Member]

Davinder,

Once again, this really depends on your organisation but especially on their ability to review the logs generated.

Most people tend to use Firefighter for just temporary elevated access in emergency scenarios. The expecation is that it is only used infrequently and therefore, the logs that are generated are reviewed in detail by the controllers.

As I'm sure you have noticed, the tool is much more powerful than that but using it as a blanket control for all system changes means that you will be innundating your controllers with logs. This actually weakens the control as they are much more likely to miss critical activities due to the volume of data being sent to them.

I would assess what you actually think is a critical change and design Firefighter scenarios to fit those. You can then also use that as a mechanism to remove critical access from business as usual roles citing Firefighter as a more controlled approach.

You can tailor the scenarios to different tiers eg. Emergency and then a subset of sensitive transactions (e.g. SCC4 / SARA with delete) but it must be lead by the business requirements for what is the overall risk to the system.

Simon