<?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: ITAR - ABAP Secure Programming in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/itar-abap-secure-programming/m-p/3112528#M738988</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Prashant&lt;/P&gt;&lt;P&gt;ITAR deals with export regulations concerning also cryptographic products.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general there is (by default) no crypto contained in SAP R/3 4.7 that falls under ITAR. However, if you start to modify or add ABAP code and include any crypto functionality, you are responsible to adhere to ITAR yourself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually the SAP secure programming guide dictates to SAP programmers to include any cryptographic functionality (when needed) as a "pluggable function". This means that the code must be able to run without crypto, even if it is then not safe.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope that this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards, Kristian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Dec 2007 08:03:17 GMT</pubDate>
    <dc:creator>kristian_lehment</dc:creator>
    <dc:date>2007-12-12T08:03:17Z</dc:date>
    <item>
      <title>ITAR - ABAP Secure Programming</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/itar-abap-secure-programming/m-p/3112527#M738987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;I would like to know whether there is any information available on ABAP Secure programming to adhere to ITAR in SAP R/3 4.7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would appreciate if you give any pointers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Prashant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 12:23:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/itar-abap-secure-programming/m-p/3112527#M738987</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-29T12:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: ITAR - ABAP Secure Programming</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/itar-abap-secure-programming/m-p/3112528#M738988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Prashant&lt;/P&gt;&lt;P&gt;ITAR deals with export regulations concerning also cryptographic products.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general there is (by default) no crypto contained in SAP R/3 4.7 that falls under ITAR. However, if you start to modify or add ABAP code and include any crypto functionality, you are responsible to adhere to ITAR yourself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually the SAP secure programming guide dictates to SAP programmers to include any cryptographic functionality (when needed) as a "pluggable function". This means that the code must be able to run without crypto, even if it is then not safe.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope that this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards, Kristian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2007 08:03:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/itar-abap-secure-programming/m-p/3112528#M738988</guid>
      <dc:creator>kristian_lehment</dc:creator>
      <dc:date>2007-12-12T08:03:17Z</dc:date>
    </item>
  </channel>
</rss>

