<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engagement Archive on MeteSec</title><link>https://metesec.com/engagements/</link><description>Recent content in Engagement Archive on MeteSec</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>metesec@outlook.com (Mete Demirci)</managingEditor><webMaster>metesec@outlook.com (Mete Demirci)</webMaster><copyright>© 2026 Mete Demirci</copyright><atom:link href="https://metesec.com/engagements/index.xml" rel="self" type="application/rss+xml"/><item><title>SOC Capability Development</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid/><description>&lt;p&gt;The engagement connects day-to-day SIEM engineering with the operating routines required to sustain a security capability.&lt;/p&gt;
&lt;p&gt;Work is documented here at a public portfolio level. Internal architecture, security data, configurations, and operational details are intentionally excluded.&lt;/p&gt;</description></item><item><title>Managed Detection &amp; Response Onboarding</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid/><description>&lt;p&gt;This engagement focused on connecting technology, responsibilities, and stakeholder expectations before operational service delivery.&lt;/p&gt;
&lt;p&gt;The archive records the engagement structure without exposing internal systems, controls, or customer security information.&lt;/p&gt;</description></item><item><title>Security Governance Remediation</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid/><description>&lt;p&gt;The central task was not simply to close individual findings, but to convert them into operating structures that can be understood, owned, and evidenced.&lt;/p&gt;
&lt;p&gt;Only the public engagement scope is described. Findings, evidence, control gaps, and internal documentation remain confidential.&lt;/p&gt;</description></item><item><title>eHealth Security Architecture</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid/><description>&lt;p&gt;The work combined architecture-level reasoning with practical security rollout support in a regulated digital-health environment.&lt;/p&gt;
&lt;p&gt;No internal design, threat scenario, endpoint detail, or implementation information is included in this public case file.&lt;/p&gt;</description></item><item><title>SOC Process Development</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>metesec@outlook.com (Mete Demirci)</author><guid/><description>&lt;p&gt;This engagement treated documentation as part of the operating system of a SOC rather than as a separate administrative artifact.&lt;/p&gt;
&lt;p&gt;The public summary excludes internal procedures, automation logic, security systems, and operational data.&lt;/p&gt;</description></item></channel></rss>