Files
2nd/10_Wiki/Topic_Programming/Architecture/Social_Engineering.md
T
Antigravity Agent 9148c358d0 docs(10_Wiki): 위키 전체 재구성 — Topic_* 폴더를 4개 카테고리로 통합 + 대규모 중복 제거
Topic_Agent/Topic_Blog/Topics/Topics_Biz/Topics_Meeting/Topics_Rag의 마크다운 지식 문서를
Topic_General/Topic_Programming/Topic_Graphic/Topic_Business 4개 카테고리로 재분류.

- 중복 제거: frontmatter의 status:duplicate/merged + duplicate_of/redirect_to 필드로
  자기 자신을 중복으로 선언한 리다이렉트 stub 1032개 제거, 완전 동일 내용 파일 472개 제거,
  동일 파일명·다른 내용 충돌 시 더 큰(완전한) 버전만 유지(162개 제거) — 총 1639개 중복 제거.
- 분류: 폴더 단위로 명확한 항목(AI_and_ML/Coding/Architecture 등 → Programming,
  Comfyui/Visual_Effects → Graphic, Topics_Biz/Topics_Meeting/사업 등 → Business,
  Poetic_Blog_Writing/창의성/Game_Design 등 → General)은 폴더 우선순위로,
  나머지 혼재 폴더(Topic_Agent/Topic_Blog/Topics 루트/Thinking & Reasoning/Other/UI_UX_Assets)는
  title/tags 키워드 스코어링으로 파일 단위 분류(불명확한 경우 General로 폴백).
  원본 폴더명은 "From_*" 서브폴더로 보존해 추적 가능성 유지.
- 최종 배치: Programming 2784 / General 1608 / Graphic 285 / Business 249 = 4926개 문서.
- 에이전트 운영 상태(.astra/.agent/.obsidian/sessions/memory/_company/docs/lessons/_shared/src)는
  지식 콘텐츠가 아니므로 재분류 대상에서 제외하고 원위치 유지.
- Topics/Topic_email(상위 보호 폴더 Topic_email과 파일명 100% 중복) 삭제 — 보호 폴더 자체는 미변경.
- 완전히 비게 된 Topic_Agent/Topic_Blog/Topics_Biz/Topics_Rag 폴더 제거.
2026-07-05 00:33:48 +09:00

4.7 KiB

id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack
id title category status canonical_id aliases duplicate_of source_trust_level confidence_score verification_status tags raw_sources last_reinforced github_commit tech_stack
wiki-2026-0508-social-engineering Social Engineering 10_Wiki/Topics verified self
Social Engineering Attacks
Human-Layer Attack
Phishing Family
none A 0.9 applied
security
threat-model
phishing
awareness
2026-05-10 pending
language framework
english security

Social Engineering

매 한 줄

"매 attack 의 weakest link 의 human 의 exploit. Tech-stack 의 hardening 보다 매 human-layer 의 manipulation 가 cheaper.". 매 phishing, vishing, pretexting, baiting 의 family — 매 2026 LLM-generated voice clones / deepfake video 가 매 attack vector 의 industrialize 했음. 매 SOC2 / ISO27001 의 awareness training 의 mandate.

매 핵심

매 attack vectors

  • Phishing (email) — bulk credential harvest.
  • Spear-phishing — targeted, OSINT-backed.
  • Vishing (voice) — 매 LLM voice clone 의 era.
  • Smishing (SMS) — package delivery, bank scam.
  • Pretexting — impersonation (CEO fraud, IT helpdesk).
  • Baiting — USB drop, malicious download.
  • Tailgating — physical access.

매 psychological levers (Cialdini)

  • Authority (CEO impersonation).
  • Urgency ("account locked, act now").
  • Scarcity ("last chance").
  • Reciprocity ("free gift").
  • Social proof ("colleagues already responded").
  • Liking (rapport building).

매 응용 (defense)

  1. MFA (phishing-resistant — FIDO2/passkey).
  2. SPF/DKIM/DMARC for email auth.
  3. Awareness training + simulated phishing.
  4. Approval workflow for wire transfers (out-of-band verify).
  5. Zero-trust + least-privilege blast radius limit.

💻 패턴

DMARC enforce policy

_dmarc.example.com. TXT "v=DMARC1; p=reject; rua=mailto:dmarc@example.com; pct=100"

Phishing simulation framework (gophish API)

import requests

api = "https://gophish.local/api"
headers = {"Authorization": "Bearer TOKEN"}
campaign = {
    "name": "Q2 Awareness",
    "template": {"name": "Fake-IT-Reset"},
    "url": "https://landing.local",
    "groups": [{"name": "All-Employees"}],
}
requests.post(f"{api}/campaigns/", json=campaign, headers=headers)

FIDO2 webauthn (phishing-resistant)

const credential = await navigator.credentials.create({
  publicKey: {
    challenge: serverChallenge,
    rp: { name: 'example.com' },
    user: { id, name: email, displayName: name },
    pubKeyCredParams: [{ alg: -7, type: 'public-key' }],
    authenticatorSelection: { userVerification: 'required', authenticatorAttachment: 'platform' },
  },
});

Wire-transfer out-of-band verify (Slack bot)

bot.command('/verify-wire', async ({ command, ack }) => {
  await ack();
  const challenge = generateOTP();
  await sms.send(command.user_phone, `Wire verify code: ${challenge}`);
  await db.storeChallenge(command.user_id, challenge);
});

Email header anomaly detection

def is_suspicious(msg):
    spf = msg.get('Authentication-Results', '')
    if 'spf=fail' in spf or 'dkim=fail' in spf:
        return True
    if msg['From'] != msg['Reply-To']:
        return True  # display name spoof
    return False

Deepfake voice detection (2026 ML)

from transformers import pipeline
detector = pipeline('audio-classification', model='WavLM-deepfake-2026')
result = detector(audio_path)
# returns: [{'label': 'synthetic', 'score': 0.94}, ...]

매 결정 기준

상황 Approach
Email account compromise risk DMARC reject + FIDO2 MFA
Wire transfer fraud (BEC) Out-of-band callback verify
Voice impersonation Codeword + callback to known number
USB drop Endpoint policy block autorun
Insider awareness Quarterly simulated phishing

기본값: FIDO2 passkey + DMARC reject + quarterly training + out-of-band approval for $X+ transfers.

🔗 Graph

🤖 LLM 활용

언제: threat-model human layer, security training content, BEC playbook. 언제 X: 매 actual phishing template generation — abuse risk.

안티패턴

  • SMS-only MFA: SIM-swap vulnerable — FIDO2 prefer.
  • Annual training only: 매 retention low — quarterly + simulation.
  • Trust caller-ID: 매 trivially spoof — callback to known number.

🧪 검증 / 중복

  • Verified (NIST SP 800-50, Mitnick "Art of Deception", Verizon DBIR 2025).
  • 신뢰도 A.

🕓 Changelog

날짜 변경
2026-05-08 Phase 1
2026-05-10 Manual cleanup — SE attack vectors, Cialdini levers, FIDO2/DMARC defenses