Skip to content

Security Hardening & Infrastructure Exposure Lifecycle Diagnostics

License

Notifications You must be signed in to change notification settings

Georges034302/SHIELD-framework

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

46 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

SHIELD Logo SHIELD®

Security Hardening & Infrastructure Exposure Lifecycle Diagnostics Framework

A systematic black-box security assessment toolkit for web applications.


What is SHIELD?

Black-box security assessment framework that executes 69 checks across 6 layers — from TLS/headers to backdoor detection and infrastructure exposure. Produces graded reports (A–F) with severity ratings, remediation code, and OWASP references.

No server access. No exploitation. No disruption.


Assessment Steps

Step What We Test
1 — Scope (3 checks)Target resolution, WordPress detection, authentication validation
2 — External Hardening (16 checks)Security headers (HSTS, CSP, X-Frame, X-Content-Type), TLS versions/protocols/ciphers, certificate expiry/transparency, OCSP stapling, HTTP→HTTPS redirect, cache controls, server/technology disclosure, PHP version exposure
3 — Auth & Session (11 checks)Endpoint discovery, login rate limiting, brute force lockout (opt-in), CAPTCHA detection, cookie flags (Secure/HttpOnly/SameSite), session rotation on login, 3-minute timeout test, logout invalidation, username enumeration (REST API + timing), WordPress user exposure
4 — Authorization (19 checks)Unauthenticated admin path access (20+ paths), API authentication, CORS misconfiguration, directory listing, file upload validation, backup file exposure (.sql/.zip), path traversal, dangerous HTTP methods, GraphQL introspection, cloud storage ACLs. WordPress: wp-config exposure, debug mode, plugin CVEs, XML-RPC, installed plugins, dangerous plugins (code execution), file editor access
5 — Backdoor Detection (12 checks)Obfuscated JavaScript (eval/atob/String.fromCharCode), hidden iframes, cryptominers, SEO spam cloaking, webshell path probing (c99/r57/wso/shell), exposed credentials (.env/.git/id_rsa), phpinfo exposure, threat intel (Spamhaus/AbuseIPDB/Google Safe Browsing), verbose error pages, open redirects, SRI enforcement, OWASP defensive controls (10+ checks)
6 — Infrastructure (8 checks)Open port scan (37 ports: databases, control panels, backdoor ports), DNS security (SPF/DMARC/DNSSEC/CAA records), certificate transparency logs, subdomain enumeration, WAF detection (Cloudflare/AWS/Akamai), shared hosting indicators, infrastructure file exposure (.git/.docker/composer.json)

Authenticated Tests (WordPress)

Pass --user and --pass to enable deeper testing:

  • Session timeout: 3-minute wait to verify session expiration
  • Logout security: Validates session invalidation after logout
  • Session rotation: Confirms session ID changes on login
  • Plugin enumeration: Lists all installed plugins with versions
  • Code execution detection: Flags dangerous plugins (WPCode, Insert Headers, file managers)
  • File editor access: Tests if theme/plugin editors are accessible (DISALLOW_FILE_EDIT check)

Quick Start

git clone https://github.com/Georges034302/SHIELD-framework.git
cd shield-framework

# Basic scan
bash scripts/run_all.sh https://example.com

# With options
bash scripts/run_all.sh -o /tmp/results -t 15 https://example.com

# WordPress authenticated scan (requires authorization)
bash scripts/run_all.sh --user admin --pass 'password' https://example.com

# Brute force lockout test (requires authorization)
bash scripts/run_all.sh --brute-force https://example.com

# Full scane with brute force scan and authenticated scan (requires authorization)
bash scripts/run_all.sh --brute-force https://example.com

Output

# Report: test_output/report.md

Report includes:

  • Security grade (A–F)
  • Priority findings (Critical/High at top)
  • Per-step issues table (FAIL/WARN only)
  • WordPress-specific section (when detected)
  • Remediation code (Apache/Nginx/PHP/WordPress)
  • Out-of-scope boundaries

What SHIELD Does NOT Scan

  • Server filesystem (webshells on disk, file integrity)
  • Database content (SQL injection payloads, stored XSS)
  • Internal networks (SSRF targets, private services)
  • Memory/processes (running backdoors, privilege escalation)
  • Source code (code review, SAST analysis)

For these: Use server-side tools (WP-CLI, Wordfence, Maldet, Lynis) or penetration testing with infrastructure access.


Requirements

bash 4+, curl, jq, dig/nslookup, openssl, nc (netcat), python3 (optional)


Authorization

⚠️ Only scan systems you own or have explicit written authorization to test.


License

Copyright © 2026 Georges Bou Ghantous®. All Rights Reserved. — see LICENSE
Use, reproduction, modification, and distribution require explicit written permission from the copyright holder.



                                                                                                                                                                                           © 2026 SHIELD   Georges Bou Ghantous

About

Security Hardening & Infrastructure Exposure Lifecycle Diagnostics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages