Warning: session_start(): Session cannot be started after headers have already been sent in /opt/lampp/htdocs/subdomains/tornado/index.php on line 2
DevWiki — Engineering Knowledge Base & Markdown Macro SSTI (Tornado)

Knowledge Base Runbook & Wiki Macro Editor

Python Tornado
Open Clean Doc View Search Docs

Article Content & Tornado Macro Tags

Macros: {{wiki.space}} {{author.name}} {{wiki.version}}
Tornado Evaluated
Tornado Engine
Template Engine: Python 3.12 (Tornado Template 6.4)

Live Documentation Runbook View

Docs Infrastructure & Runbooks Runbook

Production Cluster Ingress Recovery Runbook

Elena Rostova
Last revised September 2026
4,310 reads
Infrastructure & Runbooks
Summary: Standard operating procedure for edge proxy failover and BGP route redirection during traffic spikes.
Document Notice

Maintained by Elena Rostova (Lead Site Reliability Engineer) for the DevOps & SRE Knowledge Base team. Version: v2.4.0.

1. Architecture Overview

When external ingress proxies experience latency degradation exceeding 120ms, automatic failover diverts traffic to the secondary edge cluster in DevOps & SRE Knowledge Base.

# Verify current ingress connection health kubectl get ingress -n production -o wide curl -I -s -o /dev/null -w "%{http_code}" https://ingress.edge.internal/healthz

2. Automated Escalation Matrix

Severity Trigger Condition On-Call Contact
SEV-1 Packet loss > 5% across edge nodes elena.rostova@devwiki.internal
SEV-2 p99 Latency > 250ms for 3 minutes Secondary SRE Pager

3. Verification & Metrics Verification

Ensure that connection pools have returned to nominal capacity before resolving the PagerDuty incident record.

How SSTI occurs in Wikis & Blogs:

Many internal wikis, documentation hubs, or CMS platforms allow dynamic macros (e.g. {{wiki['space']}}). When user articles or titles are passed directly into the template compiler, attackers can inject arbitrary Python statements like:

Expression test: {{ 7*7 }}
Arbitrary execution: {% import os %}{{ os.popen('id').read() }}