Experience

Security operations grounded in real infrastructure

I am Richard Craig Lissaman, a Senior Cyber Security Analyst in Calgary. My experience spans enterprise infrastructure, systems administration, SRE-style operations, automation, monitoring, backup and disaster recovery, and security operations, so I understand how threats hide in weak visibility, how incidents disrupt operations, and how to improve detection, reporting, and recoverability in practice.

Before you publish. Add your exact employers, titles, and dates to the timeline below and align with LinkedIn. The capability themes on this page reflect skills I stand behind; attribution to specific organizations must be accurate.

Core capability areas

Security monitoring and visibility

Hands-on work with monitoring, observability, alerting, and security visibility, including Prometheus and Alertmanager. I know how to instrument systems and services so operational issues and suspicious patterns surface earlier, with less noise where tuning allows.

Log collection and centralized visibility

Experience centralizing logs from Linux (including rsyslog), Windows, servers, applications, web fronts such as Nginx, and infrastructure components, supporting monitoring, investigation, reporting, and fewer blind spots.

SIEM and security analytics platforms

Practical use of QRadar, Wazuh, Winlogbeat, Filebeat, OpenSearch, and Kibana for ingestion, dashboards, investigation, and security-aware operations, not slide-deck familiarity.

Posture improvement and remediation

Partnered with technical teams to implement fixes from penetration tests and assessments. Posture work includes hardening, control improvement, operational discipline, and follow-through, not just finding problems.

Identity, access, and policy

Security-focused device policy and control enforcement, synced security groups, SSO access workflows, and disciplined provisioning, examples include settings classes such as DisallowDigestAuthentication and DoNotAllowDriveRedirection where policy requires.

Secrets and credential hygiene

Work with Delinea Secret Server, secure handling of secrets in infrastructure and automation, automation around secret deactivation, and secure Git authentication patterns (e.g. personal access tokens) where appropriate.

Incident readiness, resilience, and recovery

Strong background with Veeam backups, validation, replication, failover, failback, and disaster recovery planning. Cyber security is prevention and response, continuity, and recoverability, especially for ransomware and infrastructure failure scenarios.

Infrastructure and platform credibility

Windows and Linux administration; VMware; enterprise servers, storage, networking, and production troubleshooting, including SMB limitations, hardware, and reliability, so security recommendations respect operational reality.

Secure automation and operational maturity

Terraform, Azure DevOps, Ansible, Python, and Bash for provisioning, deployment, monitoring setup, and repeatable operations. Security improves when environments are consistent, controlled, and documented.

Reporting and business communication

Leadership needs visibility and confidence, not raw alert floods. I focus on meaningful reporting, executive clarity, and partnership with both technical staff and business owners.

Representative timeline (add your verified roles)

Current · Calgary / remote

Senior Cyber Security Analyst, [Organization]

Summarize scope: monitoring/SOC-style responsibilities, platforms owned, SMB or enterprise context, and outcomes (e.g. reduced MTTR, improved log coverage, pentest closure rate). Use real dates.

[Years]

Infrastructure / operations / security-adjacent roles

Tie earlier roles to how they inform current analyst judgment: automation, DR, enterprise platforms, incident response support, etc.

Related pages

About · Platforms & capabilities · Certifications · Blog · Media kit

Experience FAQ

  • Do you list every technology you have touched?

    No. I highlight what is most relevant to SMB cyber security outcomes; detailed stack discussions belong in discovery and proposal, not an exhaustive public list that goes stale.

  • Can you support our stack if it is not listed?

    Often yes, principles transfer. Contact with your tooling and maturity; we will be honest about fit.