May 17, 2015
The Halliburton HypothesisQuantifying the negotiating process to mount attacks on the confidentiality of a public contract forms repository
Ansel Halliburton, friend and colleague, is always good for a great conversation.
Sometime back, Ansel and I met at Giordano Bros. on Columbus. Ansel had a new baby at home and the tired eyes to prove it. I’d just made the first preview release of the Common Form command-line tools, and Ansel was kind enough to make time for me. I don’t think anyone has helped me think as much about the confidentiality implications of ways to share Common Forms as Ansel.
Among his gems from that conversation (paraphrased):
In general, across negotiated agreements, the edit distance between successive revisions of the agreement decreases as the parties converge on an agreement.
In lawyer speak, rather than techie talk:
If you look at records for enough contract negotiations, you’ll find, as a general trend, that the amount of red in redlines passed between the parties decreases as they come closer to a deal.
All deal lawyers have done deals where this wasn’t the case. The parties may decide to switch to a different structure for the transaction, say from a stock purchase to an asset purchase. Changes in the business deal may require large changes, such as moving from cash compensation to a mix of cash and other assets. But over time, the hypothesis says, the trend is less red as you get closer to a signed deal.
One model for sharing Common Forms is to provide a public repository where anyone can add a form. No information is stored about when any form is added to the repository, or about who added it. If two successive revisions of a form are added, there isn’t any explicit link between them. Their only connection is the fact they share some provisions, the ones that weren’t revised. By the nature of Common Forms, they don’t contain names of parties, material deal specifics like amounts, dollar figures, dates, or other variable specifics. (Common Forms resemble contracts on EDGAR with confidential treatment redacted.)
The repository only allows users to request forms by their fingerprint, a unique code that reflects the content of the form. Riffling through every form in the repository isn’t allowed. You have to know what you’re looking for and ask for it. Negotiating parties can therefore store successive proposals in the repository and send the fingerprints back and forth via e-mail or some other channel they think is secure.
If a hacker takes control of the repository, however, I can’t stop them from riffing through the forms. The attacker might try to discover the particular terms of a deal between parties known to have negotiated with forms stored in the repository by creating a program to scan through the forms and search for terms or structures they would expect to appear in the targets’ agreement. They could then try to cluster Common Forms by computing edit distances and group by similarity, then review representative samples of each group to gauge the likelihood they were used by the target parties. But even if they could find a number of forms that seem to reflect a negotiation, the repository doesn’t store information about when forms were stored.
The larger the repository, the more unlikely any attacker is to discern the terms of a specific deal, and the more burdensome the task of trying. The confidentiality of the repository thus scales with the number of forms it stores. As a BitTorrent network performs better with more users, so a public Common Form repository protects confidentiality more effectively with increased use.
But if it holds, the Halliburton Hypothesis is another tool at an attacker’s disposal. Given a cluster of similar forms that seem like a probable match for the agreement of interest, an attacker might piece together the identities and order of final revisions leading up to signing by looking for edits of decreasing size. A certain amount of manual work would be required to judge the plausibility of the succession of edits, and conclusions would be educated guesses, at best, but the edit distance heuristic might be enough to make the manual task practical.
Of course, an attacker might get lucky and find that the substance of the agreement wasn’t revised much over the course of negotiation, producing lots of forms in the repository with the same provision of interest. Especially if that provision is highly particular to the transaction the attacker wants to surveil, it may be enough just to scan the repository for that provision. If the target parties are the only ones who might have added such a provision to the repository, the attacker has the exact terms they used.
On the other hand, there are kinds of information an attacker can never find. If the parties use fill-in-the-blank fields as Common Form advises (and will soon advise automatically, by recognizing problematic text patterns, like dollar figures, as they’re written), variable or “dickered” terms never appear in the repository. The attacker sees blanks the parties filled in before signing.
Nonetheless, Ansel’s hypothesis gave me pause. I’ve learned from experience in the privacy space that deidentification, the process of aggregating or redacting personally identifiable information so it can be disclosed without revealing anything about any specific individual, requires time, reflection, and deep, serious thought. Even then, bright minds screw it up all the time. Like care is required for confidentiality’s sake, and I feel this responsibility very heavily with regard to Common Form.
Your thoughts and feedback are always welcome by e-mail.
back to top — edit on GitHub — revision history