About
One person, twenty years of security work, and a habit of shipping
Anchor Velocity is Joe Carrigan. Retired U.S. Coast Guard Senior Chief, service-disabled veteran, and the person who will do your work if you hire me.
Background
Twenty-plus years in cybersecurity and intelligence operations, including assignments with the National Security Agency, U.S. Cyber Command, and Coast Guard Cyber Command. I helped establish several Cyber mission teams and was the first certified U.S. Coast Guard Information Warfare — Warfare Tactics Instructor in Cyberspace Operations.
Since June 2025 I have been a Senior Consultant with Seebald & Associates, doing maritime security assessment and plan work under federal regulation. That background is verifiable: see my consultant biography and LinkedIn profile.
Anchor Velocity is the separate thing I build under my own name: generative-AI systems, the infrastructure under them, and the security that keeps them defensible.
Why the name
Stay grounded, move faster. The anchor is structure — security, governance, testable requirements, the discipline that keeps a fast system from becoming an incident. Velocity is the other half, and it is also a deliberate reference to how delivery actually gets measured. Neither half works alone. Speed without structure is drift; structure without speed is a compliance binder nobody reads.
How I work
- You talk to me. No account manager, no handoff to a junior team after the sales call. The person you scope with is the person who builds it.
- Fixed scope, fixed price, named date. Agreed before anything starts. If I think your timeline is unrealistic I will say so instead of taking the work and missing it.
- Security goes in during the build. It is cheaper there than in a remediation project, and I have been on the remediation side enough times to know the difference.
- I test in real conditions. Live end-to-end testing, not a green mock suite. Failures show up before your customers find them.
- I show you the work. The build log on this site is public for a reason. Judge me on what I have shipped.
What I will say no to
If your problem needs a large team, a long compliance program with a national firm’s brand on it, or a specialty I do not have, I will say so and point you somewhere better. Being small only works as an advantage if I am honest about where it stops being one.
I also do not name clients or facilities. Regulated security engagements involve sensitive security information, and no case study is worth putting a customer’s exposure on a website.