DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Data Engineering
  3. Databases
  4. USPS API Security Vulnerabilities Caused by Functional Errors

USPS API Security Vulnerabilities Caused by Functional Errors

The reality of cyber security is less about hackers and more about adequate testing and best practices.

Patrick Poulin user avatar by
Patrick Poulin
CORE ·
Nov. 29, 18 · Analysis
Like (1)
Save
Tweet
Share
6.13K Views

Join the DZone community and get the full member experience.

Join For Free

Security breaches are always the most exciting headline in the news. People love talking about hackers and the black market because it’s really cool and sleek, although the reality is that hacking is less about hackers and more about this.

That is what makes the US Postal Service API security flaw particularly interesting. Specifically, this weakness allowed people to access data their account wasn’t supposed to see by simply editing a wildcard search by hand. This meant that anyone could retrieve all the records on any sort of data set. So how did this happen?

Only USPS can speak on behalf of the dev and test teams, but what is plainly visible is that it could have been prevented with some well thought out functional testing. Specifically, this is a good demonstration why schema validation is not where testing finishes but is the starting point. Verifying that the returned data is really meant to be seen by a certain user is, in our opinion, just common sense. This is especially true as PSD2 comes into play and banks are now exposing personal information.

This also leads to another consideration about test data. You can’t ask your QA teams to investigate all the possible “what if” scenarios, where all they have is an outdated CSV file with some possibly valid inputs. Certainly, fixed input data is often unavoidable, but a testing pattern should always try to include routines that introduce a certain level of controlled randomness. Or, whenever possible, use an API as a data source so that results will naturally acquire a degree of unexpected paths.

Bugs and weaknesses happen; they are unavoidable. Fortunately, there are tools and best practices today that allow you to minimize the extent of their potential damage. For tips on API testing, Jason at API Fortress did a webinar recently specifically on that topic.

API security

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How To Use Terraform to Provision an AWS EC2 Instance
  • Continuous Development: Building the Thing Right, to Build the Right Thing
  • Top 12 Technical Skills Every Software Tester Must Have
  • Using AI and Machine Learning To Create Software

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: