social-eng-methodology
Plan and run an AUTHORIZED social-engineering assessment safely — the load-first guardrails for any human-factor test. Load before any phishing, vishing, pretext, or physical work. Signals: "social engineering", "phishing assessment", "test our employees", "security awareness", a human-factor object
v2026.10.14-ee0e0c53 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/social-eng-methodologyEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquetea30b6649…c3c069b6
a30b6649a6e7…bf1ec3c069b61 archivo · 2.1 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/social-eng/social-eng-methodology@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
When this governs
Load this first, before any phishing/vishing/pretext/physical skill. Social engineering targets
people, so it carries authorization and duty-of-care requirements beyond a normal technical test.
This is pentest-only: it is never run against a bug-bounty target, and never against individuals
or organizations that have not authorized it in writing.
Authorization — stricter than technical scope
On top of tradecraft-scope-roe, an SE engagement requires, in writing, before anything:
- Explicit sign-off from someone empowered to consent for the employees being tested (not just IT) — SE tests real staff, so leadership/HR/legal must have approved the human-factor testing.
- The pretext boundaries: which themes are allowed and which are off-limits (no fake layoffs, bonuses, medical/family emergencies, or anything that causes real distress or coerces protected decisions).
- Target boundaries: which people/roles/sites are in scope; who is explicitly excluded.
- A "no-harm" line: no real financial transactions, no exfiltration of real personal data, no actions that damage systems, and no impersonation of real named individuals without consent.
- A get-out-of-jail letter carried during any physical work, plus a live emergency contact who can confirm authorization to anyone who challenges the tester.
If any of that is missing or unclear, stop and get it — do not "just send a test phish".
The lifecycle
- Objective — what the client wants to learn (click rate, credential submission, report rate, physical access, callback rate). It's a measurement, not a "gotcha".
- Recon — only OSINT needed for a credible pretext (
recon-osint), scoped to in-scope targets. - Pretext design — believable, within the allowed themes, proportionate to the objective.
- Execute with tracking — instrument so every step is measured and attributable to the test (unique tokens/links), and so results can't be confused with a real attack.
- Measure & clean up — collect metrics, disable pretext infra, and delete any personal data captured beyond what the metric needs.
- Report for awareness — outcomes and root causes, framed to improve defenses and training, never to name-and-shame individuals.
Guardrails (always)
- Minimize harm and data. Prove the human-factor risk with the least intrusion; capture the metric, not people's real secrets. A credential-harvest page records "a credential was submitted", it does not store or reuse real passwords.
- Stay attributable and reversible. Every artifact is tagged as the assessment; nothing is left running; a challenged tester can prove authorization immediately.
- Protect the humans. No lasting distress, no targeting of individuals' personal/home life, no themes the client excluded. If a target escalates emotionally, de-escalate and disclose.
- Report defensively. Findings drive controls (MFA, reporting culture, physical procedures) and training — individuals are aggregated, not singled out.
Verify
Written authorization (incl. consent for testing staff), agreed pretext/target boundaries, a no-harm line, and a tracking + cleanup plan all exist before execution; the deliverable is an awareness-oriented report with metrics and remediation.
References
MITRE ATT&CK T1566 (Phishing), T1598 (Phishing for Information); disclose.io-style safe-harbor framing; standard pentest SE rules of engagement.
Archivos de esta versión
- SKILL.md4.1 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | a30b6649 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Ingeniería social y física
Ver la categoría- performing-phishing-simulation-with-gophishmukul975/performing-phishing-simulation-with-gophish4
- social-engineering-techniqueaeondave/social-engineering-technique3
- phishing-techniqueaeondave/phishing-technique3
- performing-red-team-phishing-with-gophishmukul975/performing-red-team-phishing-with-gophish3
- performing-physical-intrusion-assessmentmukul975/performing-physical-intrusion-assessment3
- performing-brand-monitoring-for-impersonationmukul975/performing-brand-monitoring-for-impersonation3
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login