CHAPTER FOUR - THE CONSUMER FILE
Marco paced his living room floor while a team of investigators recorded the scene for evidence. Watching their activities, he knew the work was fruitless. The theft of his mobile phone had been brilliantly executed. No clues to the perpetrator would be found at the physical crime scene, the more viable search would be online, as the technologists looked for breaches in FedSec data to find the information the thief had stolen. Marco actually had three mobile phones. He hung on to one for the number he used from his last employment, and another global number he used for personal travel, but neither device was equipped with the security measures downloaded to his primary FedSec phone. And his main device, the one he kept by his bedside, contained all of his contacts and access to FedSec and other confidential government sites. Although he knew the phone carried proprietary FedSec security protections, a talented hacker could override its capabilities in a matter of minutes. The system had been tested with cooperative independent technologists who had shown his security people how external access could be attempted, but the preventative upgrades they had developed had not yet been implemented.
As an investigator approached to provide him with a summary of the situation he had already guessed, Marco stopped pacing to patiently absorb the details. The team had failed to determine the location from where the perpetrator would have operated the theft. And the type of drone model was also unknown. But based on Marco's description, they could narrow down the options and look at recent sales. The addition of the grasping claw was intriguing but not conclusive. They explained the functionality was an emerging feature and could help identify specific models equipped to attach the accessory. But to remotely manipulate the claw, the drone's camera had to revolve with the ability to look downwards and sideways. The perpetrator would be someone skilled with the equipment. Marco nodded and dismissed the investigator, the information would not advance the case or provide him with the insight he needed.
After providing another investigator instructions for closing up his apartment when they finished, he retreated to his car and drove to FedSec. Entering his office, he logged into the system, requisitioned a replacement mobile phone, and called Julia from his secure landline. After telling her details of the theft, he waited for yet another condemnation of his lack of care.
"Think about the implications of thefts by drone," Julia sympathetically responded. "No fingerprints, no digital trail, no sighting of the perpetrator, it will be cleanest crime a criminal can pull off...until COSA is built out and every drone is on the system or picked up by sensors."
"Well our covered future does not help me now," Marco angrily responded. "The claw on the drone opened my unlocked door. I'm on the 15th floor, I could never have imagined the scenario of a drone coming in through my balcony."
"No, of course not."
"The preliminary security analysis says my mobile was used to access FedSec files. The perp went after the COSA blueprint."
"We should have guessed."
"The whole document is in another set of hands."
Julia paused. "Well as annoying as that revelation is, a theft is not the worst outcome."
Stunned, Marco asked, "Why? How are you not concerned?"
"Oh I'm concerned, but we've moved on, Marco. COSA is in implementation and no longer in discussion phases. Whatever the perp thinks he's going to do with the blueprint will come too late."
"But he'll have incredible insight."
"That's okay, he won't have the program code. If your thief was a hacker, he cannot get in to the actual system with the information contained in that file."
"But he can publicize the blueprint. This time he can say he has a legitimate FedSec file and pretty clear evidence. I called the city police, the theft is public record."
"We can still deny the intention. We can repeat the entire idea is a research project with no official mandate, which is true. The blueprint does not indicate where and when COSA is to be implemented, nor do the details state which department is responsible for laying the foundation. We are on our way with this project, Marco. Whoever stole your phone waited too long to execute on a well thought out, but poorly timed crime."
"You don't think the theft is a problem?"
"The perp has literally picked up the roadmap after the asphalt has been poured. We're okay Marco, don't worry. Go home, sleep. The project is done."