<?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 Re: Implementing SAP Security in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementing-sap-security/m-p/3365269#M807548</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;gt; Is there a blueprint that I can use? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I doubt you'll ever find (a usable) one for free or on such a forum for that matter. Most of us earn (part of) our money designing them tailored to the customers' needs. I for one am surely not going to give examples away.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The best strategy will always be:&lt;/P&gt;&lt;P&gt;1- determine the needs in the company (what are the tasks for various people and which resources do they need to achieve their goals).&lt;/P&gt;&lt;P&gt;2- determine which data has to be secured.&lt;/P&gt;&lt;P&gt;3- draw a concept based on above information and have it validated by the business.&lt;/P&gt;&lt;P&gt;4- design taskroles (singles) per task and functionroles (composites) to group tasks into functions.&lt;/P&gt;&lt;P&gt;5- test both tasks and functions. The first test can be part of a unit test while the second one will be like an integration test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;People you need:&lt;/P&gt;&lt;P&gt;Functional consultants per module. They know about module-specific authorization stuff.&lt;/P&gt;&lt;P&gt;Business consultants and/or key users who know which processes there are and how they're divided over the various jobs/functions in the company&lt;/P&gt;&lt;P&gt;The (internal) auditors to tell you which information needs to be secured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you see this is not a one person job and the outcome will differ per company.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Feb 2008 08:24:47 GMT</pubDate>
    <dc:creator>jurjen_heeck</dc:creator>
    <dc:date>2008-02-06T08:24:47Z</dc:date>
    <item>
      <title>Implementing SAP Security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementing-sap-security/m-p/3365268#M807547</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For a new ECC implementation, what is the best strategy or approach to use in implementing roles and authorization? Is there a blueprint that I can use? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FYI, we are not implementing Virsa. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your response is highly appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 08:13:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementing-sap-security/m-p/3365268#M807547</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-06T08:13:21Z</dc:date>
    </item>
    <item>
      <title>Re: Implementing SAP Security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementing-sap-security/m-p/3365269#M807548</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;gt; Is there a blueprint that I can use? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I doubt you'll ever find (a usable) one for free or on such a forum for that matter. Most of us earn (part of) our money designing them tailored to the customers' needs. I for one am surely not going to give examples away.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The best strategy will always be:&lt;/P&gt;&lt;P&gt;1- determine the needs in the company (what are the tasks for various people and which resources do they need to achieve their goals).&lt;/P&gt;&lt;P&gt;2- determine which data has to be secured.&lt;/P&gt;&lt;P&gt;3- draw a concept based on above information and have it validated by the business.&lt;/P&gt;&lt;P&gt;4- design taskroles (singles) per task and functionroles (composites) to group tasks into functions.&lt;/P&gt;&lt;P&gt;5- test both tasks and functions. The first test can be part of a unit test while the second one will be like an integration test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;People you need:&lt;/P&gt;&lt;P&gt;Functional consultants per module. They know about module-specific authorization stuff.&lt;/P&gt;&lt;P&gt;Business consultants and/or key users who know which processes there are and how they're divided over the various jobs/functions in the company&lt;/P&gt;&lt;P&gt;The (internal) auditors to tell you which information needs to be secured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you see this is not a one person job and the outcome will differ per company.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 08:24:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementing-sap-security/m-p/3365269#M807548</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2008-02-06T08:24:47Z</dc:date>
    </item>
    <item>
      <title>Re: Implementing SAP Security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementing-sap-security/m-p/3365270#M807549</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks a lot!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Litz Tee on Feb 6, 2008 6:19 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 17:18:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementing-sap-security/m-p/3365270#M807549</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-06T17:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: Implementing SAP Security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementing-sap-security/m-p/3365271#M807550</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One thing to remember&lt;/P&gt;&lt;P&gt;Functional consultants MUST write a process design, this should be at TRX level and contain the needed restrictions from fucntional point of view.&lt;/P&gt;&lt;P&gt;The aforementioned should be the basis of the role design.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 18:55:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementing-sap-security/m-p/3365271#M807550</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-06T18:55:17Z</dc:date>
    </item>
  </channel>
</rss>

