OpenParable
Skip to content
← Back to skills

AT-2(3)_social-engineering-and-mining

DevOps & Security

AT-2(3)_social-engineering-and-mining is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Provide literacy training on recognizing and reporting potential and actual instances of social engineering and social mining.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/AT_awareness-and-training/AT-2(3)_social-engineering-and-mining/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/at-2-3-social-engineering-and-mining, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

AT-2(3) Social Engineering and Mining

Enhancement of: AT-2

High-Level Description

Family: Awareness and Training (AT) Framework: NIST SP 800-53 Rev 5

Social engineering is an attempt to trick an individual into revealing information or taking an action that can be used to breach, compromise, or otherwise adversely impact a system. Social engineering includes phishing, pretexting, impersonation, baiting, quid pro quo, thread-jacking, social media exploitation, and tailgating. Social mining is an attempt to gather information about the organization that may be used to support future attacks. Literacy training includes information on how to communicate the concerns of employees and management regarding potential and actual instances of social engineering and data mining through organizational channels based on established policies and procedures.

What to Check

  • Verify AT-2(3) Social Engineering and Mining is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for AT-2(3)
  • Verify enhancement builds upon base control AT-2

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AT-2(3) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

ToolPurposeUsage
Manual ReviewDocumentation and interview-basedN/A

Remediation Guide

Control Statement

Provide literacy training on recognizing and reporting potential and actual instances of social engineering and social mining.

Implementation Guidance

Social engineering is an attempt to trick an individual into revealing information or taking an action that can be used to breach, compromise, or otherwise adversely impact a system. Social engineering includes phishing, pretexting, impersonation, baiting, quid pro quo, thread-jacking, social media exploitation, and tailgating. Social mining is an attempt to gather information about the organization that may be used to support future attacks. Literacy training includes information on how to communicate the concerns of employees and management regarding potential and actual instances of social engineering and data mining through organizational channels based on established policies and procedures.

Risk Assessment

FindingSeverityImpact
AT-2(3) Social Engineering and Mining not implementedMediumAwareness and Training
AT-2(3) partially implementedLowIncomplete Awareness and Training

CWE Categories

CWE IDTitle
N/ANo direct CWE mapping

References

Checklist

  • Control documented in SSP
  • Implementation evidence collected
  • Operating effectiveness validated
  • Continuous monitoring in place
  • Related controls (none) reviewed