cloud-solution-architect

Warn

Audited by Runlayer on Mar 3, 2026

Risk Level: MEDIUM
Scan Summary
Max Score
90%
Files
9
Flagged
5
Chunks
26
Flagged Files (5)
cloud-solution-architect/references/best-practices.mdMEDIUM
89.8%

Tool passed security scan

Malicious tool definition detected

### Key Recommendations - Forward the original `Host` header from the reverse proxy to the backend - Configure Azure Front Door, Application Gateway, and API Management for host preservation - Ensure cookies are set with the correct domain matching the original host name - Verify redirect URLs reference the external host name, not the internal backend address - Test CORS configurations end-to-end with the preserved host name - Document host name flow across all network hops in the architecture #

cloud-solution-architect/references/acceptance-criteria.mdMEDIUM
88.4%

Tool passed security scan

Malicious tool definition detected

Health Modeling - Composite health score: infrastructure + dependency + application metrics - Azure Monitor with custom health model dashboard - Automated alerting at degraded/unhealthy thresholds ### 7. Security - Zero Trust: verify explicitly, least privilege, assume breach - Managed identities for all service-to-service auth - WAF policies on Front Door ### 8.

cloud-solution-architect/references/mission-critical.mdMEDIUM
84.1%

Malicious tool definition detected

- Use **Terraform** or **Bicep** for infrastructure definition with version control - Implement **zero-downtime blue/green deployment** pipelines — build and release pipelines fully automated - Apply **environment consistency** — use the same deployment pipeline code across production and pre-production environments - Integrate **continuous validation** — automated testing as part of DevOps processes - Include synchronized **load and chaos testing** to validate both application code and underlyi

**Decommission blue** — once green is fully validated, tear down the blue stamp ### Key Requirements - Build and release pipelines must be **fully automated** — no manual deployment steps - Use the **same pipeline code** for all environments (dev, staging, production) - Each stamp deployed as a **single operational unit** — never partial - Rollback is achieved by **shifting traffic back** to the previous stamp (still running during validation) - **Continuous validation** runs throughout the depl

Description: PIM, Azure Bastion | --- ## Operational Procedures ### Key Operational Processes | Process | Description | Automation Level | |---|---|---| | **Deployment** | Blue/green with automated validation | Fully automated | | **Scaling** | Stamp provisioning and decommissioning | Automated with manual approval gates | | **Key rotation** | Certificate and secret rotation | Automated via Key Vault policies | | **Patching** | OS and runtime updates | Automated via platform (PaaS) or pipeline (

cloud-solution-architect/references/design-patterns.mdMEDIUM
77.3%

Tool passed security scan

Malicious tool definition detected

Gateway Offloading **Offload shared or specialized service functionality to a gateway proxy.** **Problem:** Cross-cutting concerns such as TLS termination, authentication, rate limiting, logging, and compression are duplicated across every service. Each team must implement, configure, and maintain these features independently, leading to inconsistency and wasted effort.

cloud-solution-architect/references/design-principles.mdLOW
63.1%

Tool passed security scan

Passed Files (4)Click to expand
cloud-solution-architect/SKILL.mdOK
44.2%

Tool passed security scan

cloud-solution-architect/references/architecture-styles.mdOK
39.1%

Tool passed security scan

cloud-solution-architect/references/performance-antipatterns.mdOK
33.1%

Tool passed security scan

cloud-solution-architect/references/technology-choices.mdOK
30.7%

Tool passed security scan

Audit Metadata
Max File Score
90%
Classification
UNKNOWN_SERVER
Files Scanned
9
Files Flagged
5
Chunks Analyzed
26
Analyzed
Mar 3, 2026, 12:45 AM
Security Audit — runlayer — cloud-solution-architect