A roar of laughter burst in the room. Louie blushed.
"What were you thinking?" Alex asked, with visible amusement, yet watching carefully for his reactions. "You're not supposed to hack into anything, that's illegal!"
"No, ma'am," Louie said, "not with your consent, it's not."
Another roar of laughter. They had all known about this for a while.
"I see. I guess you're right, I did specifically invite you to hack in, didn't I?"
"Precisely. The way I read your orders, ma'am, was that you did not have the time to input your password, and you delegated the task to me."
"Lovely," Alex said.
"By the way, you have one extremely complicated password," Louie continued, "took me a full fifteen minutes to crack it."
"Oh," she said, with an admiring tone that acknowledged his ability.
"He is the meanest hacker out there, this guy, but don't tell anyone," Lisa offered.
"All right," Alex said, changing direction, "let's talk a bit about what we can expect from the aftermath of the drone incident, and how infrastructure and support needs to prepare. Thoughts, anyone?"
"First of all," Lisa said, "I don't think we were to blame at all. We do one hell of a job here, you know."
"Who do you mean, we?" Alex wanted to know for sure.
"We, infrastructure and support, this team," Lisa replied.
"It's not about putting blame on the department. The company might have a rough patch ahead of it, though, even if the company wasn't to blame. I want us to focus today on our readiness to support the larger organization, as it deals with the aftermath of all this. Regardless of who was the Florida drone's manufacturer, we still need to be ready to assist."
"We can allow access to our data, in a structured manner, with zero or little warning," Bob said. "Our systems are designed to allow quick retrievals of data and activity or service logs, to do exactly that — support potential investigations or performance assessments. We're good on this end."
"On my end, though," Alan said, "we could run into potential problems."
"Why is that?" Alex asked.
"Well, we deploy the hardware associated with the loading, testing, and deployment of the drone landmark acquisition and recognition and the target recognition software."
"And why would that put us in a hot seat?"
"Because, well, corners were cut," Alan said, looking down. "Not by us, of course, but we have knowledge of that being the case."
"What corners were cut?"
"The software testing did not occur on specs. Hardware deployment sees the activity logs and can figure out what testing had been done, and if it's up to par with the spec. You see, for all the software we deploy, we have specifications for the particular hardware that goes with it — this is what my team does. There are also clear specifications as to how software should be developed, tested, deployed, and retested. That's where the corners were cut, in the software deployment team."
"Did you report your findings?" Alex asked.
"Yes, more than once."
"What happened?"
"I was shot down, told to mind my own business."
"Did you report these findings by email?"
"Oh, sure, CYA, right?" Alan smiled sadly.
"CYA? What's that?" Alex looked confused.
"Aww… don't tell me you've worked in corporate for so long and you don't know what CYA means?" Louie laughed. "Stands for cover your ass, as in having paperwork to prove you've done your job."
"I see, well, thank you for educating me," Alex said, then turned her attention back to Alan. "Can you please forward me such emails? They would probably come in handy in the near future."
"Will do," Alan said, looking less at ease. "Other than that, we're in good shape. But if there's an official inquiry, and they ask me direct questions, I will have to tell them the truth."
"I would expect nothing else," Alex said, supportively.
"On my end," a now-serious Louie said, opening his portfolio to look at his notes, "there has been, in the past, business analysis done ad-hoc, by request of several executives, reflecting less-than-expected performance results for various areas touching infrastructure. I have also been asked, over time, to run reports for areas that were outside of the scope of infrastructure and support, such as software reliability and testing analysis reports, R&D-related reports, and so on.
"I have to confess I kept my head down on these reports. I ran the data, drew the conclusions, sent them over, and never followed up if the results were bad. Maybe I should have said something to somebody, I guess. My thinking was that if they were running the reports, then they were planning to do something to address the shortcomings, so I didn't feel compelled to do anything about the subpar performance that I found in my reports. Now, well, I don't know anymore."
"All right," Alex said, "I wouldn't worry about it now, what's done is done. Let's be ready to assist in every way possible going forward. Let's keep one another informed at all times. It's better to over-communicate issues going forward, than risk missing key information. Anything else?" Alex asked, preparing to adjourn.
Silence.
"Then, we're good. Have a great rest of the day!"
"Going out for a smoke, boss?" Louie asked, invitingly. She nodded her approval. Lisa tagged along.
Out on the lush lawn, Alex pulled her e-cig from its holder and inhaled the light vapor.
"Not doing the real deal anymore, huh?"
"Nah… stains my teeth and stinks up my house, but I can't quit either," she replied laughing.
"Listen," Lisa approached her with timidity, "there's something I wanted to tell you."
"Sure, go ahead."
"There were some people asking questions about you yesterday. Sheppard was with them."
"What people?" Alex felt her heart doubling its rhythm.
"Not sure. They wanted to know if you ever mention anything outside of work, if we ever met with you socially, if we heard you reference anything out of the ordinary, stuff like that."
"There were two men," Louie clarified, "pretending to ask casual questions, but they seemed really interested in you, specifically."
"I see," Alex said. "Does this happen often?"
"It does happen now and then," Louie said, "we are, after all, a defense contractor. We all have security clearances to be able to enter this building. Sometimes there are audits being run, just to prevent potential problems."
"Ah, then I'm sure that's OK, nothing to worry about, but thank you both for letting me know. I really appreciate it," Alex said, putting her e-cig back in her pocket.
"One more thing," Louie whispered, close to her ear, "don't ask people to forward you certain emails. You never know who's watching email traffic, do you? Then you'd both get in trouble… If you want to see Alan's CYA emails, ask him to print them. That's what printers are for."
…46
Vincent Moran's voice took a lower, more serious pitch, usually reserved for bad financial news of sizeable impact.
"After the numerous lives lost in Florida last week, as to be expected, NanoLance stock came under serious pressure from investors looking to cut their losses and liquidate their assets while their value is still notable. NanoLance lost today the biggest percentage in its trading history: 17.45 percent lost in a single day of trading. That's a cumulative 26.44 percent loss since the Florida incident last week.
"While markets were closed over the weekend, and not many investors were ready to pull out this past Monday, the volume really picked up this morning, following the News of the Hour report on the Florida drone incident. The report was syndicated nationally last night. While findings in the Florida incident are yet to come, all drone manufacturers share in the losses brought by this unfortunate incident, but NNLC, again, leads the parade of high-dollar losers on Wall Street. With shares trading now under the hundred-dollar threshold, for only $83.47 at closing bell today, NanoLance has lost its investors tens of millions of dollars, and most say this decline is not over yet.