CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

adobe/aem-6-5-lts

All AEM 6.5 LTS skills: Workflow model design, development, triggering, launchers, debugging, and triaging; Dispatcher config authoring, advisory, incident response, performance tuning, and security hardening; Replication agent configuration, content activation, API usage, and troubleshooting for AEM 6.5 LTS and AMS environments; Jackrabbit Oak query/index tuning (property, Lucene index definitions); and extracting/inventorying JCR queries (XPath, SQL2, QueryBuilder) across a codebase.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

security-baseline-checklist.mdskills/dispatcher/security-hardening/references/security-hardening/

Security Baseline Checklist

Filter Security

  • Deny-by-default posture: First filter rule is { /glob "*" /type "deny" }
  • Explicit allow rules: All allows are specific (path + method + extension/selector)
  • Admin paths blocked: /crx/*, /system/*, /bin/* (except explicitly needed)
  • Sensitive servlets blocked: /libs/*/servlets/*, /apps/*/servlets/* (unless intentionally exposed)
  • Method restrictions: POST/PUT/DELETE denied on read-only content
  • No glob wildcards in allows: Avoid /glob "*/admin" patterns
  • Selector/extension controls: Prevent bypasses like .json;.css

Cache Security

  • No auth content caching: Personalized/authenticated pages excluded
  • PII not cached: User-specific data explicitly bypassed
  • Query parameter restrictions: Only safe params allowed for caching
  • Cache invalidation configured: Proper flush rules prevent stale sensitive data
  • statfileslevel appropriate: Not too broad to prevent over-invalidation

Header Security

  • X-Frame-Options: Set to SAMEORIGIN or DENY
  • X-Content-Type-Options: Set to nosniff
  • X-XSS-Protection: Set to 1; mode=block
  • Strict-Transport-Security: HSTS enabled with appropriate max-age
  • Content-Security-Policy: Appropriate CSP policy for application
  • Referrer-Policy: Set to strict-origin-when-cross-origin or stricter
  • No version disclosure: Server header hidden or genericized
  • No technology leakage: No X-Powered-By, X-AEM-Version headers

SSL/TLS Configuration (AMS)

  • TLS 1.2+ only: SSLv2, SSLv3, TLS 1.0, TLS 1.1 disabled
  • Strong ciphers: No MD5, RC4, DES, or export ciphers
  • Server cipher preference: SSLHonorCipherOrder on
  • Valid certificate: Not expired, not self-signed (production)
  • Certificate chain complete: Intermediate certs included
  • OCSP stapling: Enabled if supported

Access Control

  • Virtual host restrictions: Only expected hosts accepted
  • IP allowlisting (if required): Restricted admin access from trusted IPs
  • No directory listing: Options -Indexes
  • No .ht file access: .htaccess and .htpasswd blocked
  • No sensitive file extensions: .bak, .old, .tmp, .swp blocked

Information Disclosure Prevention

  • Error pages sanitized: No stack traces or server file paths in errors
  • Directory browsing disabled: Options -Indexes
  • Version info hidden: Apache/dispatcher versions not disclosed
  • Server file paths not exposed: No file system paths in responses
  • Sensitive data not logged: No passwords/tokens in access logs

Logging & Monitoring

  • Security events logged: Filter denies, auth failures, errors
  • Log rotation configured: Prevent disk exhaustion
  • Log integrity protected: Logs not world-writable
  • Sufficient log retention: Adequate for incident investigation
  • No sensitive data in logs: PII, credentials excluded

Immutable Files (AMS)

  • Immutable files unmodified: No changes to AMS immutable files
  • Include structure preserved: Default includes not removed
  • Baseline drift monitored: SDK diff-baseline checks pass

General Configuration

  • Least privilege principle: Only necessary modules loaded
  • No debug mode: Production configs have debug disabled
  • Secure defaults: No insecure fallback configs
  • Configuration comments minimal: No sensitive info in comments
  • File permissions correct: Configs not world-writable

Compliance-Specific (if applicable)

PCI-DSS

  • Strong cryptography (TLS 1.2+)
  • No cardholder data in logs
  • Access controls on payment pages

GDPR/Privacy

  • No PII caching
  • User consent for tracking cookies
  • Data minimization in logs

SOC2

  • Audit logging enabled
  • Access controls documented
  • Change management for configs

Severity Mapping

Check FailedSeverityRationale
Deny-by-default missingCriticalFundamental security posture
Admin paths accessibleCriticalDirect system compromise
Auth content cachedCriticalData exposure
TLS 1.0/SSLv3 enabledHighVulnerable to attacks
No HSTS on HTTPSHighMITM vulnerability
Method restrictions missingHighWrite operations possible
X-Frame-Options missingMediumClickjacking risk
Version disclosureLowInformation leakage
Missing CSPMediumXSS risk (app-dependent)

MCP Tool Mapping

Check CategoryPrimary MCP ToolCommand Example
Filter rulestrace_requestTest sensitive paths
Cache securityinspect_cacheVerify no PII cached
Header directivesvalidate + lintVerify configured security headers in vhost/httpd config
Header propagation hintsinspect_cacheInspect cached object metadata for header behavior clues
Config validityvalidateSyntax and policy checks
Anti-patternslintSecurity rule violations
Immutable filessdkBaseline drift check
Security eventstail_logsAnomaly detection

skills

dispatcher

README.md

SKILL.md

README.md

tile.json