Adversary Based Design

Basics

• A Method of Review wherein the Product/Policy Proposal is approached via a Reviewing Party acting as the "Adversary"
• The Adversary's goal is to break the device/system
• For instance if the product being tested was a paper shredder, they would figure out how to make it fail, as well as ways to injure oneself/cause damage (within reason) using the device
• If it were a Video Game, they would do everything they could do to "Break the Game"
• If it were a Tax code, they would figure out every loophole they could use to their advantage
• An Currently Existing Example would be Penetration Testing for (Cyber-) Security Applications
  • This entails a group hiring companies/individuals who specialize in "pen-testing" to essentially hack their system, so they can then repair any exposed bugs / vulnerabilities
    • A Related concept is "White Hat Hacking"
  • It can also be done for Physical Security (Ie sneak into / break into this building)
• Another good example is Lockpicking / Safecracking (See Lock Picking Lawyer (YouTube Channel ), which, at least in the case of safes, is done by the company to determining how long it would take to destructively "cut into" a safe etc
• It Does Differ to Existing Implimentations in so far that the adversary Based Testing / Destructive Testing plays a far more active role in the design process
• ie rather that "We are finished with the design, off to testing"; from day one the design team is thinking "How can i break this / how could someone break it" thus it can also be more of a Design Philosophy at times rather than purely a testing protocol

Internal Links

• Competition Based Design
• Rapid Iteration / RITE Method
• Destructive Testing
• Evidence Based Charity / Evidence Based Philanthropy
• Peer Review