Its worth noting that yesterday’s computer-information evidence models were all self attested.
They were someone testifying about some report which means “that some events happened”. This evolved to a form where ultimately people would just jump to the conclusion and if it looked correct assume each substage of a workflow was operating properly… how little we understood fraud and deception in those days from a digital standpoint.
A prime example: Front-running in securities trading
Lets look at a real interesting phenomenon today called front-running in trading. There has been a lot of turmoil in the industry about this practice where the Trading Agent’s computers are programmed to trade the Trading Firms own shares prior to making large purchases on behalf of its clients. This allows the Agents to buy and sell stock they are absolutely positive will be influenced by transactions they themselves are about to initiate on someone else’s behalf meaning that they are exposed to Insider Information.
This creates a two fold problem, that is that the Trader is operating in their own self-interests against that of their client’s and in exercising insider information about financial matters the Client entity is ‘doing’ such that front running is more than simply unethical, it’s also likely much more than that.
So how could you catch a firm running a front running process? Simple, secure time stamping of everything at every stage. For each chain link in the chain of custody there must be timestamped records and at any instant from the point that a trade order is communicated and the trading agent is then operating on insider informaiton, they should be locked out of trading that same or related stocks in the market as a peer of the client’s they represent.
Building Culpability in the Digital Domain
No longer is the output alone of some process enough to show “it” (the process) happened properly it must be capable of having each key step retraced through the infrastructure which processed that request and for each stage entry and exit timestamps are necessary.
The answer to all of this is third-party attestations for time-stamping and time management. The Securities firm operates under their own IT security model with the addition of a third-party managed time service at the perimeter or their networks and integrated as a peering attesting voice for each key server under time-service management.
For more information on securing corporate records and meeting FINRA OATS 7430 in a manner which can document no front-running was possible, contact Certichron at 800−511−2301 or email us at Sales@Certichron.COM.
