I think the argument leading up to that conclusion is also interesting:
"Whether disclosure is a breach of duty therefore depends in large part on the purpose of the disclosure. This standard was identified by the SEC itself in Cady, Roberts: a purpose of the securities laws was to eliminate 'use of inside information for personal advantage.' 40 S.E. C., at 912, n. 15. See n. 10, supra. Thus, the test is whether the insider personally will benefit, directly or indirectly, from his disclosure. Absent some personal gain, there has been no breach of duty to stockholders." [1] (My emphasis.)
Surely the 'thus' is unjustified here, given that the quote from the SEC is a purpose of the laws, not the purpose; some other purpose of the law might establish additional tests for a breach of duty. Furthermore, the quote from the SEC does not limit the purpose of the law to situations where the leaker is the beneficiary, yet that is claimed to be part of the conclusion that follows from it.
For completeness, I will point out that the next sentence says "And absent a breach by the insider, there is no derivative breach." This cannot be used to establish that no breach has occurred, because it is predicated on that assumption.
[1] https://casetext.com/case/dirks-v-securities-and-exchange-co...
There is a fiduciary duty of care, though that has mostly to with care in the execution of corporate policies and transactions. I do not know how that has been interpreted in the context of information security.
The reasoning of Dirks seems to be that the relevant duty is the duty of loyalty, because the purpose of the law is to eliminate the "use of insider information for personal gain." So while copying sensitive information into a USB may breach one's duty of care, it's not a breach of the duty of loyalty and not within the scope of the law.
Here's how it plays out, from board rooms to halls of Congress: I breach my loyalty so that you make $1million profit. Your spouse buys my child a $50K car as a birthday present.
In the cloudy eyes of the law, I received no benefit from giving you the tip.
"The SEC argues that, if inside-trading liability does not exist when the information is transmitted for a proper purpose but is used for trading, it would be a rare situation when the parties could not fabricate some ostensibly legitimate business justification for transmitting the information. We think the SEC is unduly concerned."
The last sentence is not immediately followed by any argument in support, so at this point I have no idea why the majority would dismiss the SEC's concern, which looks plausible to me. Perhaps they think it is not a relevant concern, but if so, why not say so? Irrelevance would seem to offer a stronger counter-argument than a disagreement over the magnitude of an effect. Perhaps they are uninterested in considering this issue because they have already decided the case on what they think are logical grounds.
proof_of_breach <-> proof_of_benefit
You are arguing that it could be the case that: proof_of_negligence -> proof_of_breach
proof_of_negligence -> (proof_of_benefit v ~proof_of_benefit)
in which case there could be a contradiction.However, there is probably an argument that:
proof_of_negligence -> (proof_of_benefit v ~proof_of_benefit)
is wrong and that there actually is a rule: proof_of_breach -> proof_of_benefit
For example, if someone is negligent, we already know they received a personal benefit (eg. reduced cognitive load, received compensation for work not performed, etc.).To show a logical incorrectness, you need to show an `x` where:
proof_of_x -> (proof_of_breach ^ ~proof_of_benefit) v (~proof_of_breach ^ proof_of_benefit) proof_of_negligence -> (proof_of_benefit v ~proof_of_benefit)
easily simplifies to true
and therefore doesn't need a case to be made for it. It's always true.The argument made was that negligence could occur without benefit (ie. proof_of_negligence does not imply either proof_of_benefit or ~proof_of_benefit).
My argument is that `proof_of_benefit -> proof_of_negligence` and that `proof_of_negligence -> (proof_of_benefit v ~proof_of_benefit)` (or otherwise) is nonsense.
Exclusive or, being a logical relationship, is allowed in propositional logic. It is traditionally indicated, in mathy areas, by the symbol ⊕, but you can just compose it from the standard and, or, and not operations.
And (proof_of_benefit ⊕ ¬proof_of_benefit) still simplifies to true, unless you're a hardcore constructivist.
Newman follows from that assumption: breach of duty requires personal gain, so you cannot know duty has been breached unless you know there was personal gain. If you don't know there was personal gain, you can't tell simple negligent disclosure apart from breach of duty. And if you don't know about the violation of the duty, you can't be held liable for violating it derivatively as a tipee.