<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic fire fighter in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148170#M991889</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; From my understanding the use of fire fighter is for emergency access in PRD. For that we can just create separate ID in sap system with almost sap_all authorization (not sap_all) and access PRD whenever there is a need.But why we need sap VIRSA fire fighter or SAP GRC super user privilege management?.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Jul 2008 06:12:39 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-07-21T06:12:39Z</dc:date>
    <item>
      <title>fire fighter</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148170#M991889</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; From my understanding the use of fire fighter is for emergency access in PRD. For that we can just create separate ID in sap system with almost sap_all authorization (not sap_all) and access PRD whenever there is a need.But why we need sap VIRSA fire fighter or SAP GRC super user privilege management?.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jul 2008 06:12:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148170#M991889</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-21T06:12:39Z</dc:date>
    </item>
    <item>
      <title>Re: fire fighter</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148171#M991890</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Virsa Firefighter allows for tracking of who connects where, and what they do while connected. If you assign a generic SAP "super user", you loose these important tracking and auditing features... unless, of course, you create your own tracking system (for instance by activating a user exit upon login, demanding the person who logs in using the "super user" to identify him/herself and store some vital info such as time, date, ip address of the terminal used to connect and so on). Also, you'd need to turn security audit logging on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firefighter gives you all of these security mechanisms in one package, one which tastes good to your auditors, too... &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jul 2008 07:18:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148171#M991890</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-21T07:18:36Z</dc:date>
    </item>
    <item>
      <title>Re: fire fighter</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148172#M991891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;More specifically, Virsa firefighter will tell you which tcodes were executed and may be able to tell you which master tables were accessed (I believe table logging has to be activated). And its all bundled into one report.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jul 2008 12:22:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148172#M991891</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-21T12:22:23Z</dc:date>
    </item>
    <item>
      <title>Re: fire fighter</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148173#M991892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We use the Fire Fighter ids to assign to our suport staff a unique FF ID to each individual so  that they can use to access authorizations beyond their normal access; this allows them to address issues in a timely manner and most importantly, we receive an audit report of what they actually executed; this allows us to provide emergency support quickly and with the audit reporting facility obtain what the user has executed and review it; this sits well with the auditors when they want to know how we handle emergency needs and how is it monitored&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jerry Synoga&lt;/P&gt;&lt;P&gt;Ryerson Inc.&lt;/P&gt;&lt;P&gt;630-758-2021&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jul 2008 14:22:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148173#M991892</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-22T14:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: fire fighter</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148174#M991893</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FireFighter uses the STAT tables that are created by the program RSCOLL00.  Therefore if the information you require is not captured in these tables then FireFighter does not report on it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AC 5.x FireFighter does NOT require table logging to be turned on.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Jul 2008 08:56:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148174#M991893</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-29T08:56:34Z</dc:date>
    </item>
    <item>
      <title>Re: fire fighter</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148175#M991894</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is crucial with Firefighter that access be temporary and a strong structure be developed for evaluating the Firefighter logs.  Without these two items Firefighter actually becomes a audit liability for your IT department.  The only concern with using a SAP Most approach can be the creation of SOD's within Firefighter or access to sensitive data.  Internal and External audit are reviewing Sod's which exist within Firefighter accounts and the authorizations available.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 23:04:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fire-fighter/m-p/4148175#M991894</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-04T23:04:41Z</dc:date>
    </item>
  </channel>
</rss>

