<?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 How to prevent brute force attacks on iFrame? in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-to-prevent-brute-force-attacks-on-iFrame/m-p/71053#M43726</link>
    <description>&lt;P&gt;I have a website using the hosted iFrame on the addPayment page (&lt;A href="https://accept.authorize.net/customer/addPayment" target="_blank"&gt;https://accept.authorize.net/customer/addPayment&lt;/A&gt;).&amp;nbsp; A hacker is starting with this page, then seems to have a script that tries hundreds of card numbers per minute until the page successfully saves.&amp;nbsp; Last night between 2:42:31 AM EST and 2:48:39 AM EST (about 6 minutes), 2993 attempts were made, each causing a test transaction (Test transaction for ValidateCustomerPaymentProfile.) which is an AUTH_ONLY for $0.00.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's about 8 attempts per second!&amp;nbsp; Doesn't Authorize.Net have basic brute-force prevention in-place to prevent such an obvious attempt?&lt;/P&gt;</description>
    <pubDate>Fri, 13 Mar 2020 03:24:39 GMT</pubDate>
    <dc:creator>TroyW</dc:creator>
    <dc:date>2020-03-13T03:24:39Z</dc:date>
    <item>
      <title>How to prevent brute force attacks on iFrame?</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-to-prevent-brute-force-attacks-on-iFrame/m-p/71053#M43726</link>
      <description>&lt;P&gt;I have a website using the hosted iFrame on the addPayment page (&lt;A href="https://accept.authorize.net/customer/addPayment" target="_blank"&gt;https://accept.authorize.net/customer/addPayment&lt;/A&gt;).&amp;nbsp; A hacker is starting with this page, then seems to have a script that tries hundreds of card numbers per minute until the page successfully saves.&amp;nbsp; Last night between 2:42:31 AM EST and 2:48:39 AM EST (about 6 minutes), 2993 attempts were made, each causing a test transaction (Test transaction for ValidateCustomerPaymentProfile.) which is an AUTH_ONLY for $0.00.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's about 8 attempts per second!&amp;nbsp; Doesn't Authorize.Net have basic brute-force prevention in-place to prevent such an obvious attempt?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Mar 2020 03:24:39 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-to-prevent-brute-force-attacks-on-iFrame/m-p/71053#M43726</guid>
      <dc:creator>TroyW</dc:creator>
      <dc:date>2020-03-13T03:24:39Z</dc:date>
    </item>
  </channel>
</rss>

