Comments on: ECC6 SE16N vulnerability and logging – UPDATED http://www.basissap.com/2009/10/ecc6-se16n-vulnerability-and-logging/ The place to come when they say it's a BASIS problem Tue, 31 Aug 2010 09:15:00 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: leonsteinhardt http://www.basissap.com/2009/10/ecc6-se16n-vulnerability-and-logging/comment-page-1/#comment-113 leonsteinhardt Tue, 13 Oct 2009 18:51:48 +0000 http://www.basissap.com/?p=233#comment-113 I strongly disagree. SE16N is an essential developer tool, in all systems including production.<br>SE16N is not a danger as long as authorization is display only. An attempt to use @SAP_EDIT then results in an authorization failure; the SU53 shows<br><br>Authorization Obj. S_DEVELOP ABAP Workbench<br> Object Class BC_C Basis - Development Environment<br> Activity 02<br> Package <Dummy><br> Object name <Dummy><br> Object type DEBUG<br> Authorization group ABAP/4 program <Dummy><br><br>Properly structuring authorizations is the appropriate response to the potential danger - not removing the tool. I strongly disagree. SE16N is an essential developer tool, in all systems including production.
SE16N is not a danger as long as authorization is display only. An attempt to use @SAP_EDIT then results in an authorization failure; the SU53 shows

Authorization Obj. S_DEVELOP ABAP Workbench
Object Class BC_C Basis – Development Environment
Activity 02
Package <Dummy>
Object name <Dummy>
Object type DEBUG
Authorization group ABAP/4 program <Dummy>

Properly structuring authorizations is the appropriate response to the potential danger – not removing the tool.

]]> By: leonsteinhardt http://www.basissap.com/2009/10/ecc6-se16n-vulnerability-and-logging/comment-page-1/#comment-108 leonsteinhardt Tue, 13 Oct 2009 11:51:48 +0000 http://www.basissap.com/?p=233#comment-108 I strongly disagree. SE16N is an essential developer tool, in all systems including production.<br>SE16N is not a danger as long as authorization is display only. An attempt to use @SAP_EDIT then results in an authorization failure; the SU53 shows<br><br>Authorization Obj. S_DEVELOP ABAP Workbench<br> Object Class BC_C Basis - Development Environment<br> Activity 02<br> Package <Dummy><br> Object name <Dummy><br> Object type DEBUG<br> Authorization group ABAP/4 program <Dummy><br><br>Properly structuring authorizations is the appropriate response to the potential danger - not removing the tool. I strongly disagree. SE16N is an essential developer tool, in all systems including production.
SE16N is not a danger as long as authorization is display only. An attempt to use @SAP_EDIT then results in an authorization failure; the SU53 shows

Authorization Obj. S_DEVELOP ABAP Workbench
Object Class BC_C Basis – Development Environment
Activity 02
Package <Dummy>
Object name <Dummy>
Object type DEBUG
Authorization group ABAP/4 program <Dummy>

Properly structuring authorizations is the appropriate response to the potential danger – not removing the tool.

]]>