Infrastructure
Servers, SAN and NAS storage, Active Directory, Exchange, VMware, and Cisco / Meraki networks. The work spans the systems behind everyday business operations.
REDHAWK LEADERSHIP / CHIEF INFORMATION OFFICER
Daryl “Crash” Craft
Technical leadership built around one responsibility: protect the people who depend on the system.
Chief Information OfficerArmy veteranSystems & network engineeringSecurity & custom development
BACKGROUND
From critical equipment to connected infrastructure.
Crash’s background begins with U.S. Army technical work in radar repair, HAWK missile fire control, and satellite communications. That experience connects to a career in systems administration, network engineering, and technology development, where equipment, access, and reliable operation have to work together.
His earlier work includes systems administration at Chicago Title / Fidelity, network and systems administration and IT management at Chiricahua Community Health Systems, global administration with Zyzxi / Patron Networks, and technology engineering and development at Neutron Data Technology.
Security
Experience with healthcare infrastructure, encryption, breach detection and prevention, penetration testing, failover planning, and custom monitoring applications informs his approach to reducing exposure.
In-house engineering
At RedHawk, Crash develops the technology in-house. Monica leads the company and contributes the graphics and public identity; Crash carries the technical implementation as CIO.
WHY HIGH SECURITY MATTERS
Trust has to survive a bad day.
Technology support gives a provider access to systems that may hold customer records, business documents, communications, camera footage, and the tools people need to keep working. Protecting that access is part of the job from the beginning.
Identity before access
Verify who is requesting access, limit what they can do, and protect credentials and sessions. Sensitive administration belongs behind an authenticated boundary.
Evidence before a verdict
A headline is a reason to investigate. It is not proof that a customer is compromised. Source dates, installed versions, exposure, and observed activity guide the next action.
Recovery before a crisis
Backups, restore checks, documented changes, and clear responsibility help turn an incident into a recoverable event instead of a permanent loss.
RedHawk’s security work is designed to keep improving: review current intelligence, test the relevant controls, investigate failures, and make changes that can be verified. High security is sustained work, with human accountability for the decisions.
See the engineering. Keep the access private.
The public showcase presents screenshots of Omega, Omnicore, and Ghostroute. It gives customers a view of the work while the operational interfaces remain protected.
View the security build showcase →