Jeff P.

Halifax, Nova Scotia, Canada · Cybersecurity Instructor

American Public University System

75 followers

About

Information security professional with over 15 years of experience specializing in IT risk management, security governance, and cybersecurity instruction. He holds a Secret Level 2 clearance and is a published author of several technical titles on Wireshark, Metasploit, and CompTIA certifications.

Specialties

  • CISO / Security Leadership
  • Cybersecurity Consulting
  • Incident Response
  • Policy & Standards
  • Risk Management

Skills

  • Governance
  • Risk Assessments
  • Security Program Management
  • E-learning Development
  • Security Architecture
  • IT Risk Management
  • Policy & ProceduresBase Academy
  • Cyber Resilience
  • Incident Response Planning
  • NIST Cybersecurity Framework (CSF)

17 skills in total

Licenses & Certifications

  • CompTIA Project+ ce Certification

    CompTIA

    Issued Sep 2025 · Expires Sep 2028

  • Certified Chief Information Security Officer

    EC-Council

    Issued Feb 2025 · Expires Feb 2028

  • CompTIA CySA+

    CompTIA

    Issued Feb 2018 · Expires Feb 2024

5 certifications in total

Experience

  • Cybersecurity Instructor, On-Base Academy

    QATARI MINISTRY OF DEFENCE

    Jan 2025 — Jan 2026

    Doha, Qatar

  • Senior Security Consultant

    MARINER INNOVATIONS

    Jan 2020 — Jan 2025

    Halifax, Canada

  • Contracted Reviewer for Consulting Group

    IT PROFESSIONAL GROUP

    Jan 2016 — Jan 2020

    Virginia, US

5 experiences in total

Education

  • American Public University System

    M.A., National Security Studies

    —

  • Purdue University, West Lafayette, IN, USA

    B.A., Russian, Mathematics

    —

Recent posts

Fatima, this is excellent. Thank you for sharing with us all. Your presentation is clean, professional, and obviously a strong tribute to so much knowledge gathered in your training.

Well done!

View post

I woke up at night wondering about Malek's Private Cloud Manager project. (okay, not really, but still hungry for an update)

[profile:7d0c73b9-4c89-4954-aba5-9aeebb469cc6:Malek ANNABI] & [profile:39231cd6-6261-4b76-9edb-ff8dfd393d10:Michael Milke] -- if you two are not yet regularly sharing homelab horror stories by now, let this be day 1. :)

View post

👉 Check out **Cyberr Canada**! Join us and be part of the conversation.

/groups/c7383237-41e2-47ef-a9ae-da94b6c19ea6

View post

@Laurent, these are all well-known protocols. But how many of us use this one?

HPHLP: Happy Partner, Happy Life Protocol

Protocol Name: HPHLP

Full Name: Happy Partner, Happy Life Protocol

Layer: Domestic Application Layer

Transport: Usually TCP — Thoughtful Communication Protocol

Default Port: 143 — “I’m Sorry”

Reliability: Best-effort, but retransmission is strongly recommended.

1. Purpose

HPHLP defines a lightweight, stateful communication protocol used to maintain emotional availability, household harmony, and long-term relational uptime between two trusted endpoints.

The protocol is optimized for low-latency empathy, high-availability affection, and graceful recovery after accidental message loss, such as forgotten anniversaries, unwashed dishes, or saying “calm down.”

2. Packet Format

Field Size Description

Version 4 bits Current version. Usually 0001, unless counseling has upgraded the stack.

Mood Flag 4 bits Indicates partner state: Happy, Hungry, Tired, Suspicious, or “Fine.”

Attention Token 8 bits Required before transmitting advice. Must be renewed frequently.

Compliment Checksum 16 bits Validates sincerity. Fake compliments are dropped.

Apology Sequence Number 16 bits Increments with each mistake. May wrap quickly.

Chore Payload Length 8 bits Indicates amount of actual help offered. Zero-length payloads are deprecated.

Listening Window 16 bits Amount of uninterrupted listening available before proposing solutions.

Affection Payload Variable Hugs, tea, snacks, errands, foot rubs, or “I already took care of it.”

3. Required Handshake

HPHLP sessions begin with a three-way domestic handshake:

SYN: “How was your day?”

SYN-ACK: “Do you actually want to know?”

ACK: “Yes. I’m putting my phone down.”

Only after a valid ACK may the session enter the LISTENING_ESTABLISHED state.

4. Control Flags

Flag Meaning

LSTN Listen without interrupting

SNCK Provide snack-based stabilization

HUG Initiate physical reassurance

APOL Apology included

FIX? Ask whether solutions are wanted

DATE Schedule quality time

DISH Voluntary chore completion

FINE Critical alert; do not interpret literally

5. Error Handling

If an HPHLP packet is rejected, the sender must not respond with:

BUT_I_WAS_JUST_SAYING

This causes immediate escalation to ARGUMENT_OVER_TCP, with possible packet capture replay from three years ago.

Recommended recovery sequence:

APOL → LSTN → VALIDATE → SNCK → CHORE

6. Security Considerations

HPHLP requires strong authentication through consistent behaviour. One-time grand gestures are vulnerable to replay attacks and do not replace daily keepalive packets.

Known vulnerabilities include:

Unpatched sarcasm

Expired flowers

Weak listening encryption

Unauthorized problem-solving

Failure to clear emotional cache

7. Keepalive Requirements

To prevent session timeout, endpoints should transmit regular keepalives:

“I appreciate you.”

“You were right.”

“I made coffee.”

“I booked it already.”

“No, that outfit does not make you look weird.”

8. Termination

Sessions must not be terminated with:

RST: Whatever

Proper graceful shutdown requires:

ACKNOWLEDGE → AFFECTION → TOMORROW_PLAN → GOODNIGHT

Failure to follow shutdown procedures may result in cold-shoulder latency, couch-based routing, or denial-of-snuggle service.

View post

[celebration:new_certification]Just earned **CompTIA Project+ ce Certification** (CompTIA)

View post

View Jeff P.'s profile on Cyberr