Credentials

Certifications & continuous learning

Formal certifications complement, but do not replace, demonstrated production experience in monitoring, SIEM, infrastructure, and automation. I list credentials carefully: everything here must match what employers and clients can verify. Update the table with your facts before launch.

Verification policy

When an issuer provides a digital badge or public verification URL (for example Credly/Acclaim for certain certifications), I link to it. I do not claim certification numbers I cannot substantiate. If a credential is in progress or expired, I label it accurately, misrepresentation is not worth the reputational risk in security.

Credentials checklist (replace with your facts)

Credential Issuer Status Verification
[Your certification name] [Issuer] Active / In progress / Lapsed (choose one) [Badge URL or “Available on request”]
[Second credential] [Issuer] , ,
Remove unused rows. Add continuing education, formal degrees, or vendor-specific certifications as appropriate.

Ongoing study & communities

Threat models, vendor roadmaps, and detection techniques change constantly. I invest in labs, vendor-neutral guidance (e.g. NIST, CIS where relevant), and practitioner communities. Writing and client work stay grounded in what runs in production; see the blog and capabilities.

Cross-links for employers. Mirror this table succinctly on LinkedIn’s Licenses & Certifications section with the same verification links. Consistency between About, LinkedIn, and this page prevents confusion during hiring.

Credentials FAQ

  • Why verification links matter

    They let employers confirm claims in seconds. I only list credentials I can substantiate, accuracy beats volume.

  • Are expired credentials listed?

    Only if labeled accurately and still relevant to the narrative (for example lapsed but historically material). Otherwise they are removed or archived honestly.