Navy SEAL Asked Her Rank As A Joke — Then Four Generals Saluted Her Immediately
Chapter 4
Theme:
Font Size:
24px
Commander Brooks, head of base security, frowns into his coffee. He's older than most of the officers here, seen enough cycles of hotshot leaders to recognize the pattern. Confidence is good, necessary even; but there's a line between confidence and carelessness, and Reese has a habit of crossing it."This consultant have proper clearance?" Brooks asks."Oh, everything was in order." Reese waves a dismissive hand. "ID checked out, paperwork probably perfect. You know how it works: someone in procurement gets a kickback, suddenly we've got civilians running around like they own the place.""Still," Brooks sets down his cup. "Might be worth having my people verify. Access to UAV controls isn't something we hand out casually.""Be my guest." Reese grins. "You'll find everything's technically legal, which is exactly the problem. Too many lawyers, not enough warriors."The conversation shifts to the upcoming training exercise: a joint operation with Army Rangers, simulated coastal insertion—three days of proving once again that SEALs are the apex predators of modern warfare. Reese is in his element, describing tactical approaches, assigning roles, making it clear that failure isn't an option.Nobody notices when Brooks slips away early, phone already to his ear, requesting a deep background check on their newest contractor.Back in the control room, the woman works through her diagnostics with methodical precision.Surface-level, everything looks routine: file access logs, system performance metrics, standard maintenance protocols that any competent technician would run. But buried in that routine, hidden in the gaps between official tasks, she's doing something else entirely: cross-referencing access patterns, tracking data flows, building a map of who touches what information and when, looking for anomalies, discrepancies—the tiny cracks in operational security that suggest someone is operating outside normal parameters.Three months ago, her orders were simple: infiltrate this base, maintain a low profile, identify the leak. Someone at this facility has been selling classified tactical data to private military contractors. Not just selling it, packaging it beautifully—timed releases that maximize damage while minimizing traceability. Whoever's running this operation understands military information architecture at an expert level, which means it's someone senior, someone with access, someone who knows exactly how to cover their tracks.The obvious suspect would be Reese. He's got the clearance, the opportunity, and certainly the ego to believe he's untouchable. But obvious doesn't mean correct. Three months of watching has taught her that this base runs on a complex web of relationships and rivalries; half a dozen people could be responsible, maybe more.So she stays quiet, stays small, lets them think she's exactly what she appears to be: just another contractor filling a technical role—forgettable, dismissible, beneath notice—until she has enough evidence to burn the whole operation down.Her screen flickers: an alert. Someone's trying to access a file she's been monitoring—equipment requisition logs for a training mission that happened six weeks ago. Nothing sensitive, except that same file was accessed twice in the past month by users who had no legitimate reason to view it.She lets the access complete: doesn't block it, doesn't flag it, just watches, records, adds it to the pattern she's building.