thebiginterview
“Companies can take a number of steps to improve their API security strategy. One early step is to teach developers about API attacks. Our survey found that only 61% of organisations are using the OWASP API Top 10 list as a focus area for their security programs.”
Where, what and whom have recent cyber attackers been targeting? Companies of all sizes and industries are targets for cyber attackers. Just within the arena of publicised API attacks in the past year, we’ve seen: the Microsoſt Exchange Server attack, coordinated by Hafnium, a Chinese state-sponsored hacking group to gain access to environments and data. Tere was the Experian hack, in which an independent
security researcher was able to garner extensive personal data, including credit scores, in a manipulated API response. Te John Deere incident, in which a whitehat hacker was able
to fraudulently push device updates affecting farming automation and GPS auto-steer. Te Peloton incident, in which a security researcher was able
to use a Peloton API to pull back customer PII including user IDs, location, weight, gender, age, and more. Two cases of LinkedIn data scraping, including information on
roughly 500 million individuals at first that eventually ballooned to 700 million.
www.pcr-online.biz
Te globally disrupting “Log4Shell” or “LogJam”
vulnerability; It was discovered to impact services across
Amazon.com, Apple iCloud, Cloudflare, Twitter, and many other victim organisations, with bad actors able to manipulate log files to insert malicious code.
How can companies look to develop a robust API security strategy? Companies can take a number of steps to improve their API security strategy. One early step is to teach developers about API attacks. Our survey found that only 61% of organisations are using the OWASP API Top 10 list as a focus area for their security programs. Explaining to developers how these attacks happen can help them harden APIs against these exploits. Second, we need to take the inverse approach and teach security teams about API incidents. We’ve seen SecOps teams that are reluctant to admit they don’t know what they’re looking at when they’re trying to parse an API security incident. Having developers explain how APIs are written, what the call and
April 2022 | 23
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52
