FA1 Digital Footprint Reduction
Description
Digital Footprint Reduction involves identifying, managing, and minimizing the online information exposure of an organization and its members. This category covers controls that limit the amount of sensitive or exploitable data available to adversaries via open sources. Reducing the digital footprint helps deny attackers the raw material for reconnaissance, thereby shrinking the attack surface accessible through defensive OSINT strategies. This focus area aligns with the Identify and Protect functions of NIST CSF, it begins with mapping out exposed assets and data (akin to asset management) and implements protections to limit public exposure. It also reflects data minimization principles found in privacy laws and standards, ensuring only necessary information is publicly accessible.
Business Rationale
In any business environment, completely hiding all information is unrealistic since companies need an online presence to operate. However, many organizations unknowingly expose far more data than necessary, which attackers can exploit. Public websites, social media, marketing materials, domain records, Git repositories, case studies, and cloud services may all leak details useful to attackers. By systematically reducing these exposures, organizations can prevent this data from falling into the wrong hands. Fewer exposed details mean fewer clues for attackers, directly reducing the likelihood of targeted social engineering or technical attacks succeeding. For example, if an attacker cannot easily find employee emails, the technology they work with, or their team structure, then it becomes far more difficult for them to craft convincing phishing campaigns or find known vulnerabilities to exploit. Therefore, digital footprint reduction provides preventive security value and peace of mind to business owners, who might otherwise be unaware of how much of their organization’s data is ‘floating’ around publicly.
FA1.SC1 Footprint Inventory and Assessment
Establish clear understanding of what information about the organization (and its key personnel) is publicly available. You can't reduce what you don't know about, therefore, the first step is a thorough OSINT assessment to map the current digital footprint.
Develop and maintain an inventory of all public-facing digital assets and data sources related to the organization.
- Corporate websites, subdomains, and microsites (e.g. marketing sites, product sites)
- Official social media accounts (company pages, executive profiles that represent the company)
- Domain name records (WHOIS information, DNS entries) and SSL certificate information
- Identify mobile apps or API endpoints that are reachable publicly
- Map cloud resources or storage buckets that are exposed to the internet (even if unintentionally)
- Document third-party sites where company info appears (press releases on news sites, job postings, case studies, vendor directories, etc.)
- Catalog personal footprint of employees, especially leadership and other high-profile individuals. This should include personal social media, blog posts, conference speaker bios, etc., which often contain affiliations to the company.
Perform regular OSINT audits by simulating an outsider's reconnaissance. Leverage the same tools and techniques an attacker would.
- Use search engines with advanced operators to find company-related data e.g. ”CompanyName confidential filetype:pdf” for leaked documents)
- Search GitHub and specialized tools to identify sensitive information in repositories (credentials, secrets, API keys)
- Query data breach databases for company email domains
- Search paste sites for mentions of the company
- Utilize specialized OSINT tools like theHarvester, Maltego, or Shodan
- Review social media and forums for company mentions
- Consider hiring professional OSINT practitioners for deeper assessment
Include in the assessment any third-party or affiliate digital assets that could indirectly expose the organization. Business partners, subsidiaries, marketing agencies, or contractors might publish information about your organization. Map every third party that handles your data or represents your brand online. For each, identify what info of yours might be on their sites (e.g. client lists, case studies naming your company, shared infrastructure). This extends the footprint inventory beyond the strict corporate boundary, recognizing that attackers will exploit the weakest link (e.g., a vulnerability on a contractor’s site leaking your project details)
- Map every third party that handles your data or represents your brand online
- Identify what information of yours might be on their sites
- Extend footprint inventory beyond strict corporate boundary
- Categorize third parties by risk level based on sensitivity of shared data
- Maintain a register of authorized data sharing agreements with third parties
- Document the specific data elements each third party is authorized to publish
- Conduct regular audits of third-party websites and services for unauthorized disclosures
- Establish notification requirements for third parties when they publish information about your organization
- Monitor third-party breach notifications for potential exposure of your data
- Identify information exposed through partner case studies, testimonials, and marketing materials
Analyze the findings from the footprint inventory for sensitivity and risk.
- Categorize discovered information (e.g. contact info, technical data, locations, documents, credentials, personal info of staff, etc.)
- Assess how each item could be abused. For example: exposed email formats and templates can aid phishing; PDF metadata might leak internal usernames; an open AWS S3 bucket might expose files; an executive’s social media timeline could reveal their travel schedule
- Prioritize which exposures are most critical to address. Focus on business critical and high-impact data first: employee and customer PII, financial data, network details (IP addresses, VPN portals), authentication data, and proprietary secrets. Also, company executives and high-risk individuals digital footprints should be prioritized
- Document the results in a risk register or report to make the case for mitigation actions
Properly retire and remove external-facing assets that are no longer in use.
- Create formal decommissioning procedures for external assets
- Verify complete removal of decommissioned subdomains and microsites
- Check for dormant accounts, pages, and profiles across services
- Monitor for orphaned DNS records and certificates
- Review search engine caches and archives for retired content
- Verify removal of company data from third-party integrations no longer in use
- Monitor internet archives for historical content that should be removed
- Ensure proper redirect handling for legacy domains and URLs
FA1.SC2 Data Exposure Minimization
Limit the amount of sensitive or organizational data that is publicly exposed. Once you have mapped your digital footprint, the next step is to proactively reduce it, by “closing the holes” that leak information. This involves scrubbing unnecessary data, tightening controls on what gets published, and establishing practices that keep data exposure to a minimum.
Based on the Footprint Assessment, remediate exposures.
- If sensitive documents were found on public webpages or repositories, take them down or protect with authentication. (For instance, a PDF of an internal policy accidentally hosted on a public site should be removed or access-restricted.)
- Take down outdated websites or subdomains no longer in use. Attackers often seek out forgotten, unmaintained web pages. Tip: Use subdomain enumeration findings to identify sites that the organization might have forgotten about (old marketing campaigns, staging, test sites) and decommission or secure them
- Address web page archives and caches that preserve sensitive historical content: Identify and remove archived website content from services like the Internet Archive’s Wayback Machine that might contain sensitive information (staff directories, technical documentation, or internal procedures that were once public). Submit removal requests to archive services for pages containing sensitive data using their established removal processes. Be particularly vigilant about archived versions of your organization chart, contact pages, or technical documentation that may reveal IT staff names, email formats, HR personnel, procurement officers, or system administrators, essentially any information that could be leveraged for targeted phishing or social engineering attacks. Consider implementing robots.txt directives to prevent future archiving of sensitive pages, though recognize this won’t remove already-archived content. For particularly sensitive historical content, consider legal removal notices if archive services are unresponsive to standard requests. Remember that archived content is often overlooked during security reviews but remains accessible to attackers conducting thorough reconnaissance.
- Remove employee personal data that “doesn’t belong” on the open internet. This could include phone numbers, addresses, or emails of staff inadvertently posted (e.g. in a public Slack channel or a document that got indexed). “Tidy up” the footprint by pinpointing and removing personal information of executives and employees from where it doesn’t belong, whether on the open web or even the dark web. Professional privacy services can assist in removal if needed.
- Secure any cloud storage or servers unintentionally accessible. If any cloud storage or servers are unintentionally publicly accessible (misconfigured Amazon S3 buckets, Google Drive links, etc.), lock them down (set proper permissions or network whitelisting). Misconfigurations are a major source of OSINT leaks. For example, open S3 buckets exposing a database backup, or other critical data, is still a significant target for threat actors.
- Scrub metadata from documents/files that remain public. Ensure that PDFs, images, etc., do not carry hidden info (like author names, software versions, GPS coordinates) that could be useful to adversaries. Use tools like ExifTool to check for metadata, then regenerate or cleanse files as needed. (See 1.5 Media and Metadata Sanitization)
- Audit Git repositories and code platforms for company data. Git repositories and code platforms (GitHub, GitLab, Bitbucket, etc.) that might contain organization data, including: official company repositories both public and private; personal repositories of employees that may reference company code, projects, or internal systems. Audit public code repositories for secrets (API keys, passwords) using automated scanners (e.g. truffleHog, GitGuardian). Remove any exposed credentials and rotate them if found.
Implement measures to limit personal identifiable information (PII) of staff available online.
- Avoid listing excessive details on company. On the company “About Us” or team pages, avoid listing excessive details. It may be necessary to list key contacts or executives but consider omitting things like email addresses or detailed bios that include personal hobbies/interests (which attackers could exploit for phishing context).
- Use general corporate contact info instead of personal contact where possible. For required disclosures (like certain executive info in filings or leadership pages), consider using general corporate contact info instead of personal contact where possible. For example, list a corporate communications email rather than a direct individual’s email.
- Encourage (or provide guidelines to) employees to sanitize their social media of company-sensitive details. Employees should understand not to post specifics about projects, internal tools (“Finally fixed our AWS S3 bucket issue!”) which signals to attackers to probe your AWS buckets, or behind-the-scenes photos of the office that reveal badges or network equipment.
- Work with HR to ensure job postings do not inadvertently reveal too much about your internal environment. Job ads can leak technical stack details or software versions (e.g., “seeking Node.js 23.x expert” tells attacker you run Node.js 23.x). Scrub such details or use generic descriptions when possible.
- Offer data broker opt-out services for employees (also see Focus Area 4: Executive Protection), removing their home addresses, personal phone, etc., from people-search sites will reduce the personal data footprint significantly.
Establish clear policies and procedures that govern what information can be made public, and how.
- Adopt data classification and handling policies. If not already in place, adopt a classification scheme (Public, Internal, Confidential, Secret) and ensure employees know that only “Public” data is authorized for external release. Everything else must be protected. Tie this into training so people think twice before posting or sending out information.
- Train communications team on sensitive data best practices and implement these into publication review workflows. Require a review (by communications or security team) before new content is published on public forums (including the corporate website, press releases, marketing materials, open-source code releases, etc.). This review checks that no sensitive info is accidentally included. For example, marketing might want to mention a big client name, have a policy on whether that's allowed and if so, ensure it's vetted by legal/PR. Similarly, engineers releasing code to open source must scrub any internal references.
- Update vendor and partner agreements regarding confidential information. Update contracts or NDAs with third parties to forbid them from exposing your confidential info. Provide partners with guidelines on referencing your company publicly. (E.g., a consulting firm case study should not publish network diagrams of your environment.)
- Encourage strong privacy settings on personal social media. As part of policy, strongly encourage that employees (especially executives and anyone in sensitive roles) use privacy controls on social media. For instance, set LinkedIn profiles to not show full birth dates, email addresses, or personal contacts, keep Facebook profiles private, etc. Provide how-to guides for configuring privacy settings and removing geotags.
In cases where information must be public but could still pose a risk, take steps to anonymize it.
- Use generic emails (e.g. info@company.com) as contact points on websites instead of listing individuals.
- If posting images or videos from company events, blur or redact any background items that show badges, computer screens, sensitive documents, or whiteboards.
- Sanitize compliance-required postings. For compliance-required postings (e.g., certain financial statements or disclosures), ensure they do not inadvertently leak internal system details. Sometimes PDFs generated from office software include author names or server paths in properties; these must be sanitized.
- When registering domains, use WHOIS privacy services or a business address/phone rather than an individual’s info. Attackers scrape WHOIS for targeting data. Many domain registrars offer privacy-protection to mask owner details - use it (aligned with Privacy by Default principle).
Continuously track the development of new OSINT tools and techniques to stay ahead of emerging threats.
- Subscribe to OSINT tool release announcements and forums
- Regularly test organizational defenses against emerging OSINT tools
- Participate in OSINT practitioner communities to stay current
- Maintain awareness of academic research in OSINT techniques
- Conduct periodic assessments with new OSINT toolsets
- Update data exposure controls based on new collection capabilities
- Monitor development of AI and automation in OSINT collection
- Train security team on emerging OSINT methodologies
FA1.SC3 Public Presence & Content Management
Manage the organization’s official public presence in a security-conscious manner. This subcategory covers how to securely maintain necessary public-facing content (website, social media, press releases, etc.) so that it informs or markets to legitimate audiences without oversharing or introducing security weaknesses.
Manage the organization’s official public presence in a security-conscious manner. This subcategory covers how to securely maintain necessary public-facing content (website, social media, press releases, etc.) so that it informs or markets to legitimate audiences without oversharing or introducing security weaknesses.
- Scrutinize web content for sensitive info before publishing. Remove internal comments in HTML or code that might reveal system info. Ensure no admin interfaces are publicly accessible (attackers often find hidden paths). Disable or remove debug messages and console logging that could leak sensitive implementation details, stack traces, database query information, or internal path structures to browser developer tools. Even seemingly harmless console output can reveal sensitive information, variable naming conventions, or application architecture that attackers can leverage for targeted exploits.
- Use robots.txt and search engine guidelines appropriately. Use a robots.txt file and meta tags to prevent search indexing of sensitive areas if any. For example, if you have a partner portal login page, you might disallow it in robots.txt so it’s not easily discoverable in search engines. Note: Attackers also check for the presence of robots.txt to discover admin pages. Though security by obscurity is not enough, it can reduce casual discovery.
- Configure webserver to avoid leaking technology banners. Avoid leaking technology banners. Turn off or customize server signatures (e.g. “Apache/2.4.1”) so it isn’t shown on error pages. Also, ensure error messages on the site are generic and don’t reveal file paths or SQL errors.
- Review content delivery and caching practices. If you use a CMS, keep it updated and remove default pages (like WordPress sample pages) which OSINT tools might flag. Use a Web Application Firewall (WAF) or CDN that can mask some info and also block obvious scrapers if necessary
- Audit analytics and third-party scripts for data leakage. Be mindful of third-party analytics or trackers on your site. These can leak data (e.g., if you use a tracking script that’s compromised or if the analytics dashboard is public). Stick to reputable services and review what data they collect. Ensure no sensitive data is passed in URLs or page content that third parties or bad actors can access.
Apply guidelines for official social media accounts.
- Establish coherent messaging policy. Have guidelines on what topics can be shared. Refrain from sharing internal schedules or details (e.g., “Our CEO is now traveling to X for a meeting”) should perhaps be shared after the fact if at all, and never in advance.
- Limit geo-tagging in posts. Turn off automatic location tagging for official posts. Geospatial OSINT (GEOINT) can track routines.
- Review images and videos for sensitive details. Similar to above, ensure any multimedia posted is reviewed. A group photo in the office might show employee badges or a screen with sensitive info. Do a “background check” on all media. Use image editing to blur sensitive details.
- Monitor engagement for potential phishing attempts. Keep an eye on replies or interactions that might try to phish through social channels. For instance, a malicious actor might reply to customers with a fake support link. Ensure the social media team knows how to spot and report such behavior. While this is not exactly a footprint, it should be part of secure use of these platforms.
- Avoid mixing personal and official accounts. Whenever possible, don’t use personal accounts for official communications. For example, executives might have personal Twitter accounts. If they use them for business announcements, that account becomes a target for OSINT (and hacking). It may be better to have official accounts or at least enforce strong security (MFA, unique passwords) on any personal account that is used professionally (this extends into Focus Area 4: Executive Protection).
Manage what information is released in external communications.
- Review press releases for sensitive details. These often include quotes from executives, project details, partner names, etc. Ensure press releases are reviewed by security-minded personnel if possible, such as announcing a new tech partnership. Coordinate with IT to confirm it doesn’t unintentionally confirm use of a certain software that you haven’t patched yet, etc. Balance business needs with security.
- Vet conference presentations and publications. If employees speak at conferences or write articles, have a lightweight vetting process. Often, speaking abstracts or slides are posted online. They shouldn’t expose more than necessary about internal processes. Security teams can give a quick glance to ensure nothing sensitive is in a publicly shared slide deck.
- Monitor online reputation on review platforms. Public reviews (Layoff.com, Glassdoor, Yelp, etc.) and news can reveal issues (e.g., an unhappy ex-employee might spill info). While you can’t control everything said externally, maintain awareness (which is covered in Focus Area 5: Continuous Monitoring and Response) and respond or mitigate when possible. For example, if a review mentions too much about internal projects, you might request the platform to remove it if it violates any policy.
- Respond to information leaks via reviews or news by establishing a simple triage process. Assess the sensitivity of leaked information and potential impact on security or operations. For significant leaks, consult legal counsel about takedown options. For less critical disclosures, document the leak and consider if internal policies need revision. Avoid overreacting to minor disclosures, as this can sometimes bring more attention to the information.
- Implement heightened controls during high-risk periods like product launches or acquisitions. Create temporary communication policies with clearer approval chains and pre-approved talking points. Brief all staff who might speak externally about exactly what can and cannot be discussed. Consider increased monitoring of corporate social accounts during these sensitive periods to quickly catch and address any oversharing.
- Establish streamlined approval workflows for external communications based on risk level. Low-risk communications might need one approver, while high-sensitivity content requires multiple reviews. Create simple templates that guide content creators toward appropriate disclosure levels. Maintain basic documentation of approvals for audit purposes, particularly for communications that discuss technologies, partnerships, or internal processes.
- Create practical guidelines for remote work video environments that help employees recognize and remove sensitive information. Focus on common issues like visible whiteboards, calendars, sticky notes, screen content, or documents that might be visible in the background. Provide a simple checklist employees can reference before joining external calls to ensure their environment doesn't inadvertently expose organizational details.
- Develop a small set of approved virtual backgrounds for staff who regularly represent the company externally. Ensure these backgrounds are professional but don't contain sensitive information like unreleased products or organizational details. Test backgrounds with various platforms to confirm they work reliably without glitches that might momentarily reveal actual surroundings.
Be aware that content can inadvertently reveal technology stack or security posture.
- Posting a job “seeking SIEM manager experienced with Splunk and AWS” tells an attacker you use Splunk and AWS, which they can use for attacks. Strive to keep technology mentions broad or generic in public posts (“experienced with SIEM tools”).
- Press releases about digital initiatives might mention platforms such as “we migrated to Salesforce Cloud…”. If such details are not sensitive, this is low risk, but if they give away something critical such as “…with MFA from XYZ vendor”, now attackers know what MFA you use and might look for its weaknesses and exploits, be cautious.
- Even images of office or employees might show brand logos of software on their computer screens or a command-line prompt with an internal server name. Train eyes to catch those.
- If you run a bug bounty, consider what gets disclosed publicly. Sometimes resolved vulnerabilities are posted; ensure those write-ups don’t provide a blueprint for others before fixes are thoroughly applied everywhere.
FA1.SC4 Privacy and Personal Data Protection
Protect the privacy of individuals (employees, executives, clients) in the context of public data, and comply with data protection regulations when it comes to public-facing information. This subcategory focuses on preventing OSINT gathering of personal data through privacy-centric controls and aligning with laws that incidentally help reduce exposure (like GDPR's right to erasure, etc.)
Systematically remove employees information from data broker sites. Focus on all personnel whose exposure could create security risks, not just executives. This includes IT staff, security personnel, finance teams, and anyone with access to sensitive systems or data.
- Identify major people-search sites and data brokers relevant to your region (e.g., Whitepages, Spokeo, Radaris, ZoomInfo, etc. in the US; 192.com in the UK; etc.).
- Use their opt-out procedures to remove or suppress your employees' data. Prioritize C-suite and high-risk individuals, but ideally cover as many employees as possible, starting with those who want it (some may volunteer their info).
- Consider using a privacy service such as Optery, that automates repeated opt-outs, as these databases often repopulate over time. Services such as Optery, offer continuous removal from dozens of brokers as a subscription. This can be an effective managed approach for executive protection.
- Educate employees on opting themselves out of commonly used databases (provide guides or even hold a workshop on personal digital privacy).
In jurisdictions with strong privacy laws, make use of legal rights to remove data.
- If an employee or the company finds personal data online that is violating privacy (or simply not desired to be public), you can send formal requests to the data controllers to delete that data. For example, a blog listing employee names in Europe, without permission can be asked to remove them (under GDPR if applicable).
- Use Google's removal tools to delist search results that expose personal info. Google has a process to remove results for things like ID numbers, bank info, etc., and even a new policy to remove personal contact info on request.
- These controls are more reactive, but having a process in place to utilize these rights quickly can contain an exposure.
Ensure design of public-facing apps and sites avoids exposing personal identifiers.
- Don't include usernames or emails in URLs (which can be seen by third parties or crawled).
- Mask customer or employee data on any public dashboards or reports. If you have a 'employee of the month' on the website, maybe use only their first name, rather than full name + picture + location, etc.
- In marketing materials, if referencing a person (like a testimonial), get their consent and limit what's revealed (perhaps first name, industry, not full name unless they explicitly agree to being a public reference).
Extend security awareness training to include personal digital privacy tips for employees.
- Explain how social media privacy settings can prevent bad actors from seeing posts. Encourage everyone to review their settings for LinkedIn, Facebook, Instagram, etc., to ensure only intended audiences see their info.
- Warn about oversharing: e.g., posting your new work badge selfie or a LinkedIn update that includes your corporate email in the image.
- Provide resources or tools (browser extensions) that flag trackers, or information on removing one's info from certain sites). Some employees may take steps to remove themselves from data broker lists if they know how.
- Highlight that privacy measures not only protect them as individuals, but also the company. For instance, if they secure their personal phone number, scammers can't easily impersonate IT support calling them.
Ensure that external privacy notices and practices align with applicable laws.
- If your company is subject to GDPR/CCPA, you likely already have to minimize personal data collection and publish privacy notices. Frame this compliance as part of security: collecting minimal data means less breach/OSINT risk.
- When customers or others request deletion of data, honor it.
- Maintain a policy to not publish personal data without consent. This is often a legal requirement, but explicitly make it a security concern too, to ensure marketing knows to ask permission before putting a client's logo or a person's name in a case study.
FA1.SC5 Media and Metadata Sanitization
Control what hidden information might be contained in media (images, documents, videos) that are published or leave the organization. Metadata and hidden data in files can be an OSINT goldmine if not sanitized. This subcategory ensures that when media is shared publicly, it is cleaned of any unnecessary details (while preserving authenticity when needed).
Establish a practice that any images published are stripped of metadata.
- Remove EXIF data from images, which often contains camera information and possibly GPS coordinates. A simple example: a photo taken on a smartphone can reveal the GPS location of the office if not removed. Tools such as ExifTool can batch-remove such metadata.
- Also remove other metadata like Photoshop edit info, which might have usernames or software versions.
- If sharing screenshots, be mindful of what's in the screenshot (e.g., a username, URL, or email address).
- If images are of people, consider whether faces of employees should be blurred for privacy if it's not necessary to identify them.
Cleanse office documents of metadata before publishing.
- Office documents (Word, PDF, Excel, PowerPoint) often contain: Author names, Revision history, Hidden comments, and file path locations of where it was edited (which can give insight into internal network or user names).
- Use tools or settings to wipe this. For example, MS Office has a 'Document Inspector' feature that can remove comments and author properties. PDFs can be sanitized via Acrobat or other PDF tools.
- Before publishing any document externally (like documentation to customers, press releases, or research papers), run through a metadata removal step.
- Also ensure no hidden sheets or hidden text remains in documents (attackers sometimes find hidden rows in Excel sheets or leftover redlined text).
Manage metadata from devices used to create content.
- Ensure camera devices used for official purposes have geotagging turned off by default. For example, a field services team taking photos should disable location tagging if those photos might go into public reports.
- PDF printers or other software sometimes stamp info like 'Printed by [username] on [machine name]'. Configure such software to not include those details.
Consider physical OSINT in media beyond digital metadata.
- Train employees not to leave sensitive information in view when taking photographs (even personal ones that might end up online). For example, someone taking a picture at their home office for LinkedIn could inadvertently capture a confidential document. This overlaps with the Social Engineering Defense training.
- If filming in office for a promo video, do a sweep to remove whiteboards, badges, or documents from the background (or blur them in post-processing).
- Be mindful of company logos or building addresses in photos - while not secret, they can confirm locations or identities that contribute to OSINT profiling. It's usually fine to show logo, but be aware that doing so confirms that person is at HQ or a particular location, which could be used by an attacker (for instance, to socially engineer that they visited your office).
Integrate metadata scrubbing into workflows.
- For example, if your company uses a CMS for blogging, see if there's a plugin that auto-sanitizes images on upload.
- If employees frequently need to share files outside, provide them with easy tools (and instructions) to sanitize. Perhaps a script or a simple UI where they drop a file and it returns a cleaned version.
- Regularly update these tools, as metadata formats can vary (e.g., new camera types). Keep an eye on any new channels like 3D models or AR/VR content if that ever becomes relevant, which could have their own metadata.
Spot-check files that have been released publicly to ensure compliance.
- As part of audit, occasionally download images/docs from your own website and see what info they contain. This can be part of the OSINT assessment routine, treating your own outputs as an attacker would.
- If something is found with metadata that shouldn't be there, treat it as an incident and improve the process, and remove that file if possible or replace it.
FA1.SC6 Historical Information Management
Identify, control, and where appropriate, remove historical organizational information that persists in archives, caches, or legacy platforms and may present OSINT risks.
Identify and manage organizational content stored in internet archive services.
- Regularly scan archive.org and similar services for sensitive historical content
- Implement appropriate robots.txt directives to limit future archiving
- Submit removal requests for sensitive historical information
- Monitor archive sites for newly captured historical content
- Establish ongoing archive monitoring as part of the security program
Manage and remove sensitive information from search engine caches.
- Use appropriate cache control headers for sensitive web content
- Submit urgent cache removal requests for critical exposures
- Implement appropriate meta tags to control indexing and archiving
- Maintain documentation of cache removal procedures
- Verify removal of cached content across multiple search engines
Properly retire and sanitize legacy platforms and services.
- Develop formal decommissioning procedures for legacy systems
- Conduct OSINT assessment of legacy platforms before removal
- Ensure complete data sanitization during retirement
- Verify removal of all public-facing components
- Document historical system inventory for incident response purposes
Control access to and availability of historical organizational documents.
- Conduct periodic reviews of historical publications and filings
- Implement redaction procedures for historical documents when republished
- Create an inventory of sensitive historical documents
- Assess risk of information in historical annual reports and SEC filings
- Develop controls for legacy document repositories and archives
FA1.SC7 Mobile Application OSINT Exposure
Address the unique OSINT risks created by mobile applications developed by or used within the organization.
Control what information is revealed through app store listings and metadata.
- Review app descriptions for sensitive organizational details
- Limit developer information that could be used for targeting
- Sanitize screenshots for sensitive information before publishing
- Consider privacy implications of app permission descriptions
- Regularly review and update app store content
Secure mobile application APIs against OSINT reconnaissance.
- Implement robust API authentication mechanisms
- Remove unnecessary information from API responses
- Obfuscate API endpoints and structure
- Monitor for unauthorized API access that may indicate reconnaissance
- Conduct regular security assessments of mobile APIs
Implement controls to prevent information leakage through mobile apps.
- Use code obfuscation to prevent reverse engineering
- Implement certificate pinning to prevent traffic analysis
- Remove debugging information from production builds
- Ensure secure local storage of sensitive information
- Limit logging and error messages in production apps
Regularly assess organization mobile apps for OSINT exposure.
- Conduct security testing from an attacker's perspective
- Use mobile app security scanning tools
- Review app binaries for hardcoded credentials or endpoints
- Test information exposure through intercepted traffic
- Verify privacy controls function as intended
FA2 Social Engineering Defense
Description
Social Engineering Defense encompasses policies, training, and technical controls aimed at preventing, detecting, and responding to attacks that trick people (users or employees) by exploiting information and trust. OSINT is often the first step for social engineering, and attackers gather personal and organizational details to make their deception more convincing. This focus area is about strengthening the human element of security so that even if attackers know some things about your organization, they cannot easily manipulate people or processes. This aligns with NIST CSF Protect (Awareness and Training) and Detect/Respond functions, as it involves educating users and establishing procedures to identify and react to social engineering attempts. It also aligns with Zero Trust, which in a human sense means “never trust, always verify” requests even if they come with familiar details.
Business Rationale
Social engineering such as phishing, pretext phone calls, baiting with USBs, and so on, is one of the top ways breaches occur because it targets the most unpredictable factor, human behavior. Attackers rely heavily on OSINT to improve their success rates in these attacks. For instance, knowing an organization’s internal project names or the org chart, helps craft a believable phishing email (“Hi Alice, as per Project Zeus meeting with Bob…”). Defending against social engineering is critical to protect financial assets (fraudulent wire transfers), credentials (phished passwords), and system access. A threat actor only needs to have a single successful social engineering attack, in order to bypass layers of technical security. Businesses must create a culture of skepticism and verification, especially for SMBs, where every employee often has broad access. A single mistake can be devastating, and for enterprises, social engineering is often how attackers bypass complex defenses (e.g., spear phishing an admin). This focus area ensures that employees and processes are resilient against such manipulation, minimizing the impact of OSINT available to attackers.
FA2.SC1 Security Awareness and Training
Educate and empower all members of the organization to recognize and resist social engineering attempts, with special emphasis on how attackers use OSINT to make those attempts credible.
Incorporate specific modules in security awareness training that demonstrate the connection between what people share and the attacks they might face.
- Show employees how an attacker might gather their data from LinkedIn or Facebook and craft a phishing email that references their recent post or a colleague's name. This makes training visceral, as they see how attackers exploit publicly available information to build trust.
- Include a segment on recent real-world incidents in the news where companies were breached due to social engineering and highlight what info was used.
- If possible, use sanitized findings from your own OSINT assessments to personalize the training ("We found out X, Y, Z about our team online; imagine an attacker using that in a phone call."). This often gets employees' attention. Do not shame employees, this must be about education and empowerment.
- Emphasize to executives on how their public profiles can be misused such as deepfakes or impersonation using their publicly available videos or audio (YouTube, podcasts, etc.). Ensure training is enterprise-wide, including all executives and the board, not just for lower-level staff.
Make training recurrent, not one-off. Social engineering tactics evolve, and people may forget.
- Annual comprehensive training for everyone (with a test to ensure comprehension).
- Frequent micro-trainings or reminders (monthly newsletters, short videos, posters) focusing on current threats. For example, "Beware of emails claiming 'updated HR policy' as attackers know we're merging with X company etc."
- Use interactive exercises such as phishing email simulations, or even role-playing tabletop exercises. Security teams can stage a controlled fake phone scam to see if an employee verifies identity, then use it as a teaching moment.
- Provide positive reinforcement for employees who report suspicious activities, to encourage engagement.
Conduct internal phishing simulations and other social engineering tests to assess training effectiveness.
- Periodically send simulated phishing emails to employees (with appropriate transparency or at least eventually letting them know it was a test). Track click rates, report rates. Use results to identify who needs more help or which departments might be targeted.
- Consider extending simulations beyond email, such as simulated vishing (voice phishing) call exercise to a sample of employees (ensure this is done carefully and ethically, possibly with prior consent or in a training context). There are services that can simulate phone or SMS phishing.
- For high-value targets such as finance, conduct targeted spear-phishing tests that mirror what a real attacker might do (with management's approval) to ensure even sophisticated lures are recognized.
- After simulations, provide immediate feedback and learning materials. If someone fell for a phish, don't shame them; rather, educate them on the clues that were missed.
Encourage an organizational culture where it's okay to verify and double-check requests.
- Ensure employees know that security will never punish them for failing to verify an unusual request. Often, attacks succeed because employees fear upsetting a supposed boss or breaking 'urgency'. Make it clear that taking a moment to confirm is always the right choice, this is far better than rushing into a potential scam.
- Provide simple verification channels: e.g., if someone gets a request seemingly from the CEO, they should know they can directly call the CEO's office or check with IT before acting. Formalize an easy process, like an internal verified phone directory or a security hotline to ask "Is this real?".
- Promote stories of "secure behavior" internally. Celebrate an employee who refused to divulge info to an unknown caller even though they knew some personal details, and indeed it turned out to be a phishing attempt. This positive reinforcement makes others more confident to do the same.
- Personal responsibility and vigilance: as Steve Durbin suggests, foster the idea that each person is responsible for what they share and how they react. Encourage them to treat corporate info with the same care as personal financial info. For example, "you wouldn't give your bank details to a stranger, so treat company secrets similarly."
Provide specialized training for employees more likely to be targeted due to their access.
- Finance teams on BEC scams: training on how attackers spoof CEO or vendor emails to request wire transfers and establishing strict verification for any payment changes. Include specific training on payroll fraud, W-2 phishing, fake vendor schemes, and invoice fraud using insider knowledge of business processes.
- IT helpdesk staff on verification of callers: an attacker might pretend to be an employee with an urgent IT issue. Teach helpdesk staff to verify identity beyond what might be found on social media (like not resetting a password just because caller knows the user's employee ID and birthdate). Implement code words or secondary authentication methods for high-privilege requests.
- Executives and board members: aside from general training, brief them on specific cons like "VIP phishing" (attackers sending personalized emails or invites). Also, ensure they understand not to override security protocols in the name of convenience, as this not only sets bad precedents if execs routinely ask staff to bypass process, but attackers will learn to exploit that pattern. Include quarterly briefings on current executive-targeting campaigns and deepfake threats.
- System administrators (CRM, HR, financial systems): focus on social engineering attempts targeting administrative access to critical business systems. Train on recognizing sophisticated impersonation attempts using insider knowledge of business processes and implement dual-authorization requirements for critical system changes or sensitive data access requests.
- Engineers and R&D teams: educate on industrial espionage techniques and social engineering targeting intellectual property. Include awareness of conference and networking event risks where technical details might be socially engineered, and establish protocols for handling requests for technical information from unknown contacts.
- HR teams: provide intensive training on employee data protection, recognizing fake employee verification requests, and sophisticated schemes targeting personal identifiable information. Establish multi-person approval processes for sensitive HR data requests and implement verification procedures for employee data requests and benefit changes.
- Legal and compliance teams: focus on social engineering attempts to access confidential legal documents, regulatory filings, and privileged communications. Train on recognizing fake legal requests, fraudulent court documents, and establish verification procedures for urgent legal document requests from unknown parties.
- Vendor and supply chain managers: train on supply chain attack vectors, vendor impersonation schemes, and fraudulent vendor payment change requests. Implement strict verification procedures for vendor communications and establish secure channels for critical vendor communications and contract negotiations.
- Long-term employees: conduct enhanced OSINT awareness training showing how their extended digital footprint creates increased targeting opportunities. Provide personal digital privacy training, data broker opt-out assistance, and training on recognizing highly personalized social engineering attempts using historical professional information.
- Executive assistants and support staff: include in specialized training on gatekeeping procedures, verification protocols for executive communications, and recognizing attempts to bypass executives through their support staff. Train on handling urgent requests claiming to be from executives and establish clear escalation procedures.
Train employees to recognize how physical items can be weaponized using OSINT knowledge.
- Suspicious Conference Gifts and Post-Event Packages: Warn attendees about accepting electronic gifts (USB drives, power banks, digital photo frames) from vendors or as promotional items at industry events where their attendance was publicly known. Similarly, caution about unexpected packages delivered to the office following public events.
- Hidden Tracking and Malicious Hardware: Educate staff that seemingly benign gifts may conceal compromised electronics, tracking devices such as modified Bluetooth trackers (E.g. Apple AirTags with speakers disabled), or pre-registered gift cards that could reveal location patterns when used (they are already linked to an online account for access to transaction history).
- Executive Protection Context: Emphasize to executives and their support staff that their public appearances at conferences create opportunities for targeted physical social engineering. An attacker who knows from social media or event listings that an executive attended a specific conference might send personalized follow-up "gifts" that exploit this knowledge.
- Verification Protocol: Establish a process for safely handling unexpected electronic gifts or devices, such as routing them through IT security for inspection before use or connection to any corporate network or device.
FA2.SC2 Communication and Transaction Verification
Implement formal processes to verify the legitimacy of sensitive requests or communications, thereby thwarting social engineering attempts that rely on impersonation or fraudulent instructions.
Define what constitutes a 'sensitive request' and require independent verification.
- Examples of sensitive requests include: instructions to transfer funds or change bank details (classic CEO fraud/BEC), requests for confidential data (customer lists, employee records), password reset or MFA reset requests for privileged accounts, unusual requests from executives ("send me all W-2 forms now," could be fake).
- That means using a different and pre-agreed, communication channel to confirm the person's identity and intent. For example, if you get an email supposedly from the CFO to wire money, you must call the CFO at their known number (or secure messenger app) to confirm, not just reply to the email.
- For particularly sensitive operations, consider using end-to-end encrypted messaging platforms like Signal Messenger with verified safety numbers as a secure secondary channel, especially for executives who frequently handle confidential requests. The key is ensuring the verification happens through a separate system that would require an attacker to compromise multiple channels.
- Provide employees with accessible contact lists (verified phone numbers, etc.) for key authorizers to facilitate this. They shouldn't rely on contact info provided in the suspicious request (which is likely to be fake).
- Train everyone that "no urgent request is too urgent to verify," and scammers create urgency to bypass this, but institutionalize the rule that "if it's truly urgent and legitimate, the slight delay to verify is understood and expected".
- Use code words or shared secrets within teams if feasible. For example, some companies set up code phrases for high-level requests ("If I really send an email to finance for a wire, I'll include Project X reference in it which we agreed on, otherwise call me").
For critical transactions or data access, require at least two people to approve or be involved.
- Financial: set dollar thresholds where any payment requires two approvers, preferably via separate channels or systems. This means an attacker would need to fool two people independently, which is far more difficult.
- IT changes: No single admin should be able to reset another admin's password without a second admin's oversight in the process. Or changes to core DNS records require a second person confirmation to prevent an attacker who tricks one IT staff from redirecting the domain.
- HR data: release of bulk personal data (like responding to an email request for all employee tax info) should require a manager approval.
Move sensitive communications to authenticated, secure channels rather than open email.
- For instance, have a policy that all internal payment requests go through an internal ticketing system or finance system, one that requires login and has audit trails, instead of free-form emails. This reduces the chance of spoofed emails causing action.
- Use official company email addresses and discourage use of personal accounts for work matters (in the event of a ransomware attack). Attackers might spoof a Gmail pretending to be an exec; if everyone expects that exec only ever writes from the corporate email, a Gmail one would raise suspicion.
- Implement email security measures (DMARC, DKIM, SPF) to help prevent spoofing of your domain and to warn users if an email fails checks. While not foolproof (attackers can use lookalike domains), it does add a layer of technical defense.
- For external communications use secure portals for exchanging files with partners, so employees don't rely on emailed instructions that could be intercepted or faked.
Use technology and processes to catch impersonation attempts early.
- Email filtering: Use phishing detection tools that flag emails with suspicious traits (e.g. domain names that are one letter off, or emails that look like from a VIP but originate from outside). If possible, configure email systems to place a banner (e.g. "External email") on anything external, so if an email claiming to be from the CEO is received from an external source, the user sees a warning banner.
- Typosquatting monitoring: Keep an eye on domain registrations similar to your own (e.g., mycompany.co instead of .com). If found, you can assume phishing may follow and warn users in advance. Some threat intel services or even a simple script can do this.
- Fake social profile detection: Monitor (or have HR/PR monitor) for fake LinkedIn or other social media profiles of your executives or company. Attackers sometimes create a fake profile of a CEO and then message employees. If detected, report to the platform and inform your staff if a wave of impersonation is ongoing so they won't be fooled.
- Encourage employees to report even "weird" things like an unexpected text message or WhatsApp from someone claiming to be a colleague. Provide a channel (e.g., forward suspicious messages to security) and treat each seriously. Many targeted scams might start with a text like "Hey, it's [CEO name], are you available? I have an urgent task."
FA2.SC3 Technical Anti-Phishing and Social Engineering Controls
Deploy technical measures to reduce the success of social engineering attacks, particularly phishing. While user awareness is key, technology can prevent many traps from ever reaching or tricking the user.
Use a robust email security solution to filter out malicious emails.
- Ensure spam filters are tuned to catch common phishing indicators (links to known fake sites, malformed headers, etc.). Modern solutions use AI to detect phishing patterns and can quarantine or flag suspicious mails.
- Configure URL rewriting/scanning in emails so that if a user clicks a link, it is checked against threat intelligence or sandboxed. This might block known phishing pages or at least warn the user.
- Use attachment sandboxing: many phishing emails come with attachments (Office docs with macros, etc.). Email gateways can detonate these in a sandbox environment to see if they are malicious before delivering.
- Enforce DMARC policy to reject or quarantine emails that spoof your domain. Also, monitor DMARC reports to see if someone's trying to spoof (you'll get reports of sources that failed).
- Add visual cues in emails: as mentioned, external mail tagging ("[External]" in subject), and perhaps a warning if an email display name matches a VIP. E.g., if an email claims to be from "Jane Doe, CEO" but isn't from Jane's address, the system could flag: "This email appears to be from Jane Doe but originated outside the organization." Some advanced systems do this.
Implement protections against malicious websites.
- Use web filtering on company networks to block access to known phishing and malware-hosting sites. If an employee clicks a link to a fake O365 login, a good web proxy or DNS filtering (like using Quad9, OpenDNS Umbrella, etc.) can block the resolution and present a warning.
- Ensure browsers are up-to-date (to catch their built-in Google Safe Browsing warnings, etc., and to patch exploits).
- Consider browser extensions or email client add-ons that can flag suspicious characteristics (some security products will highlight if a domain in an email is similar to but not exactly your company's).
- If using cloud email (like Office 365 or Gmail), enable their anti-phishing features (Microsoft ATP SafeLinks, Google's advanced phishing and malware detection, etc.) which integrate across email and browsing.
Implement MFA to protect against credential theft.
- Enforce MFA on all employee accounts for email, VPN, critical applications, and especially admin accounts. Prefer app-based or hardware token MFA over SMS if possible (to avoid SIM-swap attacks, though any MFA is better than none).
- Educate that MFA codes themselves can be phished (attackers create fake login pages that ask for the code too). Address this by encouraging use of phishing-resistant MFA if feasible (like FIDO2 security keys which can't be phished easily, or at least OTP apps that show what application is requesting the code).
- Monitor MFA usage - alerts for unusual MFA approvals can indicate an attempted breach, which might trace back to a phishing incident that needs response.
Ensure strong password practices to counter information gained from OSINT.
- Implement password managers and encourage their use, so employees have unique strong passwords that aren't guessable from personal info (e.g., not using pet names or birthdays attackers might find). This ties to training but providing an approved password manager enterprise-wide can help. Avoid linking password managers to phone numbers, which can be compromised through SIM-swapping attacks. Instead, tie them to email addresses secured with long, unique passwords and protected by multi-factor authentication (MFA) using app-based authenticators or hardware keys rather than SMS.
- Use breach data checks - some systems integrate with HIBP (Have I Been Pwned) to prevent known compromised passwords. If an employee's corporate credentials were leaked in some breach, force a change. This reduces risk from credential stuffing.
- If not already, enforce complexity and length standards, and consider passphrases over complex short passwords - easier to remember, harder to brute-force.
- Avoid static shared passwords for anything sensitive; opt for unique accounts, so an attacker can't find one password and reuse it elsewhere.
Deploy honey tokens or decoys to detect malicious activity.
- For example, create fake employee records (names/email addresses that aren't real employees) and publish them subtly (maybe in website code comments or non-public pages). If you ever receive an email to that alias, you know it's malicious because no legitimate use exists. This can reveal that attackers scraped that info.
- Another example: a fake admin password embedded in an internal file (that no one should use). If someone tries to use it or if it shows up in a phishing attempt, you have an early warning that internal info was compromised.
- While this is more in the realm of threat detection than prevention, it helps identify that an attacker is actively working against you, possibly allowing a quicker response before they succeed on a real target.
FA2.SC4 Remote Work OSINT Protection
Provide additional protective measures for executives or other high-profile personnel who are prime targets for social engineering due to their influence or access. Attackers often focus on execs (CEO fraud) or use their identity to trick others. This subcategory ensures those individuals and their handlers are prepared. Note: There is overlap with the dedicated Executive Protection focus area, but here we address social engineering aspects specifically.
Develop guidelines to minimize information exposure in home working environments.
- Create standards for securing visible and audible home office environments
- Provide guidance on appropriate placement of workstations to prevent screen visibility
- Establish policies for use of virtual backgrounds or physical backdrops in video calls
- Develop checklists for employees to assess OSINT risks in their home office setup
- Implement rules about organizational content visible in personal social media
Implement controls to prevent information leakage during remote meetings and presentations.
- Create guidelines for screen sharing that minimize exposure of sensitive information
- Establish protocols for recording meetings and handling meeting artifacts
- Provide training on secure use of collaboration platforms
- Implement technical controls on recording, transcription, and file sharing permissions
- Create awareness about risks of public Wi-Fi or shared networks for sensitive discussions
Enhance security for remote connectivity to prevent OSINT exploitation.
- Implement secure VPN configurations that mask organizational infrastructure details
- Enforce endpoint security solutions that prevent data leakage
- Create guidelines for securing home networks
- Limit exposure of internal resources to potentially compromised home networks
- Conduct security assessments of remote connectivity solutions for information exposure
Establish procedures for handling physical documents in remote environments.
- Create policies for secure disposal of printed materials at home
- Implement guidelines for secure transport of physical documents
- Provide secure storage solutions for home offices
- Develop inventory management for organizational assets in remote locations
- Limit printing of sensitive materials in home environments
FA2.SC5 Incident Response for Social Engineering
Develop and implement specific incident response procedures for social engineering attempts and successful attacks, including rapid containment, investigation, and recovery steps.
Ensure it's easy for employees to report suspected phishing or social engineering attempts.
- Provide a one-click "Report Phishing" button in the email client if available, or an email address like phishing@company.com to forward suspicious emails.
- For phone or in-person attempts, have an internal number or chat channel to ping security immediately.
- Emphasize in training that prompt reporting can save the day - even if they almost fell for it or did click something, reporting fast can allow IT to intervene (e.g., by resetting accounts or blocking a malicious domain).
- Make it non-penal: people should not fear punishment or ridicule for reporting, even if they made a mistake (the goal is to fix it, not blame).
Take immediate steps when a social engineering incident is confirmed.
- If credentials are potentially compromised, then immediately trigger password resets for that user's accounts and any shared or service accounts they had access to. Check authentication logs, VPN access records, and system audit trails to determine if the attacker has already used the credentials to access systems or data. For privileged accounts, also review recent administrative actions, configuration changes, and data access patterns to identify potential unauthorized activity. If evidence of credential use is found, expand the investigation to include all systems and data the compromised account could access.
- If malware might be executed, then isolate the affected machine from the network, run scans, and consider forensic analysis to see if additional payloads were dropped.
- If fraudulent financial action happened, then immediately involve finance and potentially bank fraud departments to see if transfers can be halted or recalled (time is of the essence; many banks can freeze a suspicious wire if alerted within hours).
- If data was sent out (e.g., someone emailed files to an impostor), identify what data, inform data privacy officer if personal data is involved (potential breach notification duties), attempt to get recipient to delete it (maybe futile if malicious, but law enforcement could be engaged).
- Launch a broader alert if needed: e.g., "We have confirmed a phishing email got through filters and 3 people clicked it - all staff, do not click emails about X and delete any you find." Quick communication can prevent further harm.
After containment, investigate the incident thoroughly.
- Conduct a root cause analysis: how did the attacker reach the target? What OSINT did they use? For example, if an employee got spear phished with details that came from LinkedIn, note that. It ties back to possibly reducing that footprint.
- Gather indicators (email headers, phishing sites, IPs, etc.) and see if others were targeted. Often if one person reports, others got the same email - check mail logs to find those and see if any other clicks or replies occurred.
- If it was a phone scam, gather details of what was said, maybe the number used (though often spoofed). Use this to warn others.
- Document timeline and impact: was any account actually breached? Money lost? Data stolen?
- Engage law enforcement if a crime occurred (significant fraud, etc.). They might not always act, but having a report on file can help (especially if insurance claims are involved).
- Feed findings into updated training and controls. For instance, if the incident revealed employees are unclear about verifying payment changes, update the policy and re-communicate it.
Provide appropriate support to those affected by incidents.
- Assure the person (if an employee) that reporting was the right thing and that the focus is on fixing it.
- If needed, provide some coaching or re-training to them privately, but keep it constructive.
- If an executive was impersonated and that caused disruption, assist them in any fallout (like if their email was compromised, help them reach out to personal contacts who might've gotten weird messages).
- In some high-stress cases (like a scam that nearly tricked someone into a huge transfer), consider the human factor - maybe offer counseling if it was traumatic (some spear phishing can be threatening in tone, e.g., extortion emails).
Ensure social engineering scenarios are covered in broader incident response plans.
- Assign roles: e.g., who from security handles phishing analysis, who communicates to all staff, who interfaces with bank or authorities if needed.
- Have pre-drafted communication templates for common scenarios (like an email to employees about a phishing campaign, or a notice to clients if their info was leaked via a hoax).
- If your company falls victim to a public scam (like someone impersonated your brand to scam customers, or a fake press release, etc.), have PR involved as well to manage external communication.
- Conduct occasional incident response drills focusing on social engineering (like a table-top exercise: "An employee was tricked into giving up VPN login, attacker is now in - what do we do?" to test IR readiness in that context).
Establish resilient out-of-band communication channels for critical incidents.
- Deploy Independent Encrypted Messaging: Implement end-to-end encrypted messaging platforms (like Signal) for incident response team members and executives that operate completely outside corporate infrastructure. Configure with verified safety numbers to confirm authenticity of participants. Pre-establish group channels for different incident response scenarios. Ensure these systems are accessible via personal devices or dedicated emergency devices not connected to corporate networks. Test regularly to ensure all participants can access and use the system effectively.
- Assume Full Adversary Monitoring: Develop communication practices based on the assumption that threat actors have complete visibility into all corporate channels. Train personnel to treat all corporate email, chat, VoIP, and internal systems as compromised during active incidents. Establish verification protocols to authenticate identities when using emergency channels. Create clear guidelines about what information can be shared on which channels. Practice discussing sensitive incident details exclusively through the secure channel.
- Maintain Offline Contact Repository: Ensure critical contact information remains accessible even during complete system outages. Distribute secure physical copies of emergency contact details including Signal IDs and alternate phone numbers. Store this information in multiple locations both on-site and off-site. Include external contacts such as legal counsel, cyber insurance representatives, and incident response providers. Update regularly to reflect organizational changes.
- Regular Exercising of Emergency Communications: Practice using these channels before they're needed. Include emergency communication tests in tabletop exercises and incident response drills. Simulate complete corporate communication failures to ensure familiarity with alternate channels. Rotate responsibility for initiating these exercises across the team. Document lessons learned to continuously improve the protocol.
FA2.SC6 Canary Profiles
Establish and maintain fictitious employee profiles as an early warning system for social engineering attempts.
Design and implement believable but fictitious employee profiles across relevant platforms.
- Create realistic-looking social media profiles (primarily LinkedIn, but other platforms such as ZoomInfo) for fictional employees who don't exist. These profiles should: Have plausible job titles for potential targets relevant to your organization (IT administrator, finance specialist, HR coordinator, etc.), Include reasonable background information and education history, Feature a high quality AI-generated image that cannot be reverse-image searched, Have connections with real employees (who are aware of the canary's purpose), Occasionally post believable, non-sensitive content to maintain appearance of activity, Add misinformation on public-facing profiles, which introduce technical inaccuracies to mislead attackers without affecting legitimate operations. This creates confusion during reconnaissance, potentially causing attackers to waste resources on ineffective attack vectors.
- Deploy internal presence evidence to support the canary's existence: Create company email addresses for these personas (which forward to security team)
- Assign an owner from the security team to manage each canary profile, maintaining its believability and monitoring for contacts
Incorporate canary profiles into security awareness training and processes.
- Train all employees on the existence and purpose of canary profiles: Ensure staff understand these are security tools, not to be disclosed to outsiders, Clarify that any contact attempts supposedly from these non-existent employees should be immediately reported, Incorporate into new-hire onboarding to prevent accidental disclosure
- Create a simple reporting process for employees who observe: External parties mentioning the canary employees, Messages or calls asking about the canary, Social media connection requests directed to the canary from suspicious sources
- Ensure frontline staff (receptionists, help desk, etc.) are trained to recognize inquiries about canary profiles and have clear escalation procedures
Deliberately place traces of the canary profile where attackers conducting reconnaissance might find them.
- Position canary details to catch different types of social engineering: Technical canaries (e.g., IT admin profiles) to catch technical support impersonation, Financial canaries to detect BEC and financial fraud attempts, Executive assistant canaries to identify whale phishing attempts
- Carefully leak information that makes the canary profiles attractive targets: Place names in metadata of public documents (as "last modified by"), Include in organizational charts that might be visible in public photos or presentations, For IT profiles, create GitHub profiles with fake 'leaked' code, Mention in job postings (e.g., "Reports to Jeff White, IT Security Lead"), List as contact person for specific systems or departments on semi-public resources
- Ensure any created information is consistent and believable, avoiding over-exposure that would raise suspicion
Establish mechanisms to detect when canary profiles are targeted.
- Technical monitoring: Configure email forwarding and alerts for any messages sent to canary email addresses, Set up notifications for social media interaction attempts with canary profiles, Consider using specialized tools that monitor for mentions of canary identities across the web
- Human reporting network: Create a dedicated channel (email, chat, hotline) for employees to report any contact about canaries, Train employees that even seemingly innocuous inquiries about canaries are worth reporting, Reward and recognize employees who correctly identify and report canary-related social engineering attempts
- Response prioritization: Trigger immediate security team alerts when canary profiles are targeted, treating as high-priority security events
Use canary profile triggers as evidence of targeting.
- When canary profiles contact employees, or are referenced by external parties: Initiate investigation to determine the nature and scope of the reconnaissance attempt, Document all details of the contact attempt (sources, methods, what information was sought), Correlate with other security events or intelligence to identify broader campaigns
- Response actions following canary alerts: If a specific attack vector is identified (like phone calls from a particular number), warn all employees to raise awareness, Consider enhanced security measures for the genuine role/department being targeted, Use the information to improve security awareness training with real examples, In persistent or serious cases, consider engaging law enforcement or sharing intelligence with industry peers
- Rotate or refresh canary profiles if they become ineffective or compromised
Regularly update and maintain canary profiles to ensure continued effectiveness.
- Periodic review (quarterly or biannually): Update profile information to remain current with organizational changes, Refresh profile activity to maintain appearance of legitimate use, Verify all monitoring mechanisms are functioning properly
- Effectiveness assessment: Track metrics on profile views, connection attempts, and triggered alerts. Engage with the organizations social media team for assistance., Evaluate if profiles are believable based on the types of social engineering attempts detected, Adjust canary strategy based on changing threat landscape and effectiveness data
- Legal and ethical considerations: Ensure to maintain compliance with platform terms of service, Maintain documentation of security purpose for all fictitious profiles, Consult legal team on privacy implications and appropriate use limitations
FA2.SC7 Deepfake and AI-Generated Content Defense
Implement measures to detect and defend against sophisticated AI-generated social engineering attacks.
Establish verification procedures to counter voice deepfake attacks.
- Implement out-of-band verification for voice requests
- Create personal verification questions for executives
- Train staff to recognize signs of synthetic voice attacks
- Establish callback procedures for sensitive voice communications
- Consider voice biometric technologies for critical systems
Develop protocols to verify the authenticity of video communications.
- Establish multi-factor authentication for video meetings
- Create awareness of video deepfake capabilities and limitations
- Implement challenge-response verification for sensitive video calls
- Train employees to spot visual artifacts in deepfake videos
- Develop secure video meeting procedures for high-sensitivity communications
Implement measures to identify AI-generated communication attempts.
- Train employees to recognize patterns in AI-generated text
- Implement technical solutions to flag potential AI-generated content
- Create awareness of personalized phishing capabilities with LLMs
- Establish verification procedures for unusual text communications
- Monitor for advanced spear-phishing attempts using AI technologies
Develop robust authentication mechanisms for use during suspected deepfake attacks.
- Create emergency verification codes or phrases
- Establish secure out-of-band communication channels
- Implement physical security keys for critical authentication
- Develop incident response procedures specific to deepfake attacks
- Train security teams on deepfake detection technologies
FA3 Technology Exposure Management
Description
Technology Exposure Management is the practice of identifying, monitoring, and reducing the exposure of an organization’s IT infrastructure and technology assets to the public internet. This includes managing the attack surface (domains, IPs, devices, cloud services, etc.), addressing vulnerabilities, and controlling what technical details are discoverable through open sources. Essentially, it’s the counterpart to digital footprint reduction but focused on network, software, and hardware assets. It aligns closely with the Identify (asset management) and Protect (hardening, patching) functions of NIST CSF, as well as the Detect function (through continuous scanning). It also reflects Zero Trust principles by minimizing open access and ensuring that just because something is reachable, it doesn’t mean it’s wide open.
Business Rationale
Many breaches begin with attackers using OSINT tools like Shodan or scanning to find an organization’s weak points - an open database, an unpatched server, a forgotten subdomain. Especially in a world of cloud and remote work, a company’s internet-facing footprint can sprawl beyond headquarters’ firewall. Technology exposure leads to incidents such as data leaks, ransomware (via exposed RDP or VPN), cryptojacking (via open cloud instances), etc. For a business, uncontrolled exposure means higher risk of compromise, service outages, and compliance violations (if, say, a database with customer data is left open). Managing this exposure ensures that the organization’s online systems are known, tracked, and properly secured. It also feeds into customer trust - clients expect businesses to secure their systems, and a publicly discovered flaw can damage reputation. Furthermore, reducing exposure can lower the noise in security monitoring (fewer false alarms from unknown systems) and optimize resource focus on legitimate assets. In summary, by systematically managing technical exposures, an organization can prevent opportunistic attacks and make targeted attacks far more difficult.
FA3.SC1 External Asset Discovery and Inventory
Maintain a living inventory of all externally accessible technology assets and their attributes. You cannot protect or manage what you aren't aware of.
Compile a list of all domains owned or registered by the organization and their subdomains.
- Use tools like Sublist3r, Amass, Assetfinder to find subdomains from certificate transparency logs, DNS records, web crawls, etc.. This often reveals test environments, dev servers, third-party hosted sites (like <company>.cloudfront.net).
- Monitor Certificate Transparency feeds for any new certificates issued in your org's name (which might indicate a new subdomain or even a fraudulent domain).
- Don't forget internal project names that might have external DNS entries (e.g., an internal tool accessible via a specific subdomain for remote use).
- Include country-specific domains if applicable (like .co.uk, .cn versions).
- Align this with what marketing/IT knows. Sometimes marketing spins up microsites for campaigns - ensure security is in that loop and such microsites are catalogued.
Identify all IP address ranges owned or used by the organization.
- Check public records (ARIN/RIPE WHOIS) for IP blocks registered to the company.
- If using cloud providers (AWS, Azure, GCP), list the ranges or specific addresses in use. Use cloud provider APIs or consoles to list all running services with public IPs (VMs, load balancers, etc.). Attackers use services like Shodan to find these, so you should know them first.
- Include offices or subsidiaries with their own connections, as they might have separate IP space.
- Also track third-party services that might expose something on your behalf (e.g., a vendor running a server for you).
- Create a network diagram or table that links IPs to systems/owners for clarity.
For each discovered host, identify what services are exposed.
- Regularly scan your external assets with port scanners (like Nmap or use managed services). This should cover common ports (web 80/443, SSH 22, RDP 3389, etc.) and possibly all 65535 in depth for thoroughness.
- Use specialized OSINT search engines like Shodan, Censys, ZoomEye to see what they have indexed for your assets. Shodan might already list open ports and even grab banners/screenshots of your systems. This can reveal things like an open database port that you didn't know about or an old VPN portal with a weak cipher.
- Document which services are expected vs. which are not. For example, if a particular server should only have 443 open, but scan finds 445 (SMB) open, that's an exposure to address.
- Identify unusual open ports or services
Track cloud services and third-party components with public presence.
- Inventory any SaaS platforms that might have public-facing components. For instance, a Jira or Confluence instance that might be in cloud and possibly accidentally public, or a Box/Dropbox repository with public share links.
- If you have mobile apps or IoT devices, list the endpoints they communicate with (APIs, cloud endpoints) which might be discoverable via app analysis (attackers do reverse engineer apps to find API endpoints).
- Check for Shadow IT - employees might set up unsanctioned cloud services (a developer spins up a personal AWS instance for a test using company data). Consider using CASBs (Cloud Access Security Brokers) or cloud monitoring to catch unknown services being used with corporate accounts.
- Work with procurement to know what services have been purchased or subscribed to that could have an external presence (like an outsourced analytics dashboard, etc.).
Implement processes for ongoing discovery of new assets.
- Use an Attack Surface Management (ASM) tool or service if resources allow, which continuously scans for new assets or changes (some products specifically do this and alert on new domains, ports, etc.).
- Schedule periodic scans (weekly or monthly) for new subdomains or hosts. For example, schedule Amass or similar tools to run regularly and compare results against previous scans to identify newly discovered assets or changes to existing ones.
- Integrate with DevOps: whenever a new app or service is deployed, updating the inventory should be a required step (perhaps integrated in CI/CD pipelines or change management processes). Create automated checks that prevent deployments if asset inventory isn't updated.
- Leverage automation: deploy scripts that can cross-reference DNS zone files, cloud provider APIs, certificate transparency logs, and other sources to automatically update a central inventory database. Set up alerts when discrepancies are found between different data sources.
- Implement change detection workflows to establish processes to investigate and validate any newly discovered assets to determine if they are authorized deployments, shadow IT, or potential security threats requiring immediate attention.
FA3.SC2 Vulnerability and Configuration Management
Proactively identify and remediate vulnerabilities or misconfigurations in external-facing systems that OSINT or attacker scans could uncover.
Perform frequent vulnerability scans of all internet-facing systems.
- Use both automated tools (like Nessus, OpenVAS, Qualys) and manual verification for critical systems. Automated scans can find known CVEs, outdated software versions, etc.
- Schedule scans ideally monthly or at least quarterly, and always after major changes. Also consider ad-hoc scans when major new vulnerabilities hit the news (e.g., if "Apache Log4j" zero-day emerges and you have Apache servers).
- Include web app scanning (with tools like OWASP ZAP or Burp Suite) for your web applications to catch common issues (SQLi, XSS) that could be found by an attacker's OSINT (attackers often use Google dorks to find error messages, which indicate underlying flaws).
- Scanning should not be one-size-fits-all: authenticate where possible to see behind login pages (if any are exposed to internet) and consider API scanning for your web services.
- Ensure you scan cloud assets that might not be in traditional scope (like an open S3 bucket might not respond to a port scan but is a vulnerability if publicly accessible - use cloud config scanners for that).
Establish a process to rapidly patch critical vulnerabilities on external systems.
- Maintain an updated inventory of software and versions on each external asset (web server version, OS version, etc., possibly from the asset inventory or scanner output).
- When a critical vulnerability is announced (especially one that is exploitable via network, like a remote code execution in a web service), immediately assess if any external systems are affected. Use vulnerability feeds or scanner plugins.
- Prioritize external-facing systems in patch management - these should have faster SLA (e.g., patch critical within 7 days on externals, vs maybe 30 days for internal ones).
- If patching will delay, apply temporary mitigations: e.g., if a certain URL path is vulnerable, maybe block it on WAF until you patch; or disable a feature/module.
- Keep frameworks and dependencies updated too (e.g., the CMS version, or a Java library your site uses). Attackers will exploit known holes in things like WordPress plugins or old jQuery libraries they detect via OSINT.
Harden configuration of servers and services to minimize information exposure.
- Disable or restrict dangerous services: e.g., if an attacker finds SSH open, ensure it's locked to key authentication only and maybe IP-restricted if possible. Turn off services that aren't needed (if a server doesn't need FTP, don't have port 21 open; if an application doesn't use HTTP, redirect HTTP to HTTPS or close it).
- Banner Grabbing: Many services proclaim their software and version (like an SMTP server saying "Sendmail 4.1"). Configure them to either hide or give minimal info. Apache can be set to "ServerTokens Prod" to hide OS details, etc. This doesn't fix a vuln, but it makes OSINT a bit harder because attackers can't immediately know what version you run. It also looks more professional security-wise.
- Default Credentials: Ensure no public-facing service is left with default passwords or public read access. This includes things like network devices (firewall web interface), databases (Elasticsearch, MongoDB often hit via OSINT when open with no auth). Part of config management is to either not expose those or secure them with strong creds and allow-list IPs.
- Encryption: Configure SSL/TLS properly on all services that support it. Use strong cipher suites, disable old protocols (SSLv2/v3, TLS1.0). This prevents attackers from trivially intercepting traffic but also signals good security posture. Tools like SSL Labs test can be used to verify configurations publicly.
- Sensitive Data in Responses: Check that your public systems aren't returning too much info in errors or API responses. For example, a verbose error might reveal file paths or user IDs. Set applications to use generic error messages for outsiders.
Conduct regular penetration testing focusing on external footprint.
- Pen testers will simulate what an attacker can do with OSINT and scanning, often finding logic issues or chained exploits that automated scanners miss.
- They might use OSINT to gather employee info and test how far they can get with default passwords or public info on APIs, etc. This can reveal holes in a more realistic way.
- Use results to fix issues and also update your processes (if pen test finds an unknown subdomain, improve asset discovery; if they phish in to get in, maybe strengthen social engineering training).
- If budget is an issue, even using community resources like bug bounty programs can help identify exposures (many researchers like to find open S3 buckets or exposed admin consoles; offering a bounty could crowdsource finding such issues).
Secure remote access systems that are externally accessible.
- Ensure VPNs, remote desktops, etc., that are externally accessible are fully patched and require MFA (this was partly covered in Social Engineering with MFA, but in context, e.g., an unpatched VPN (like older Pulse Secure or Fortinet) can be found on Shodan and exploited, as seen in many breaches).
- If using RDP externally, strongly consider a gateway or at least non-standard ports and login attempt monitoring. Exposed RDP has led to ransomware; ideally avoid direct RDP exposure at all.
- For cloud management interfaces (AWS console, Azure portal) - though they are cloud-hosted, treat them as external and ensure user accounts are secure (MFA, no unneeded accounts).
- If applicable, protect any IoT or OT systems connected to internet. E.g., if you have security cameras that are viewable remotely, ensure they're behind VPN or cloud accounts, not open ports.
FA3.SC3 Managing Data Exposure in Code and Repositories
Prevent technical data leaks through source code or configuration files that are publicly accessible.
Review and secure code in public repositories.
- Review code before publishing to ensure no hard-coded secrets, credentials, or sensitive config remain. Use automated secret scanning (GitHub has secret scan, or use tools like TruffleHog).
- Remove or sanitize any internal URLs or IPs if they don't need to be public (for instance, a config file pointing to "db.internal.company.local" might reveal internal network naming conventions).
- Ensure commit history doesn't contain secrets (sometimes a secret is removed in a later commit but still present in history; in such cases, consider rewriting git history or invalidating that credential).
- If you accidentally publish something sensitive, have procedures to invalidate keys, rotate credentials quickly. Also consider GitHub's takedown or secret removal process if needed (GitHub will alert on certain secrets like AWS keys automatically and disable them).
- Monitor forks and issues of your public repos; occasionally, someone might post something sensitive there by mistake (like an intern raising an issue and pasting a stack trace with internal info).
Apply strong security measures to private code repositories.
- Use access control: only give repo access to those who need it. Remove ex-employees promptly (and check if they potentially cloned large repos).
- Enable 2FA/MFA on Git accounts. Many breaches happened because someone's GitHub account got phished, then attacker planted backdoors in code or stole code.
- Encrypt sensitive data at rest if possible; but at minimum, ensure backup of repos are secure.
- For corporate-managed repositories, consider implementing commit hooks or scanners that prevent committing secrets. For example, have a pre-receive hook on Git server that rejects commits with AWS keys pattern or certain keywords.
- Conduct periodic code audits focusing on credentials: have scripts that scan through all repos for anything that looks like a password or key.
Manage risks when sharing code with third parties or publishing packages.
- If developers publish NPM/Python packages, ensure they don't accidentally include internal files in the package (there have been cases of internal source accidentally packaged).
- If using container images (Docker), ensure images pushed to public registries don't have secrets baked in or environment variables with sensitive data.
- Attackers search Docker Hub or package managers for environment files or config artifacts.
- Also, check infrastructure-as-code templates (like CloudFormation, Terraform) that might be public - ensure they don't have static secrets or reveal too much about internal architecture.
Continuously monitor public code platforms for sensitive information.
- Set up alerts or use services that scan GitHub, GitLab, Pastebin for your domain name, IP ranges, or unique keywords. Often employees might unknowingly upload logs or code that reference the company.
- Use search queries (like "password" "company.com" on GitHub or Google) to find possible leaks. There are specialized search engines for code (like searchcode.com).
- Use the GitHub API to search for your company name or key projects regularly.
- If found, follow up with the user who posted it or use platform's abuse process if it's not your content but affects you.
Train developers on secure coding and secrets management.
- Make sure they know not to hardcode secrets and to use vaults or config management for that.
- Teach them about the risks of "leaky" code - e.g., leaving debugging info or credentials in code that gets pushed.
- Implement a robust code review culture where peers also check for any sensitive info in commits.
- Provide tools like vault services (HashiCorp Vault, AWS Secrets Manager) so they aren't tempted to put secrets in code.
- Also caution against answering too much on public forums (like Stack Overflow). Sometimes a dev might post a config snippet asking for help, not realizing it has a server name or key in it. Encourage sanitizing such info before posting.
FA3.SC4 Exposure via Third Parties and Supply Chain
Address the risk of technical exposure coming from partners, vendors, or supply chain relationships.
Include OSINT perspective in vendor evaluations.
- Check what information about your relationship they might make public (case studies, client lists - did they put your company logo on their website without you knowing? That tells attackers you use that vendor, which might have known exploits).
- Assess the vendor's own security - do they have open servers or past breaches? Some info may be publicly known (news of a breach, or Shodan shows their systems vulnerable). This might not directly expose you, but if they're interconnected it can.
- Ensure contracts have clauses about not exposing your data. E.g., a cloud provider should guarantee they won't leave your data in a public bucket, etc.
- In extreme cases, you might do a light OSINT scan on a key vendor (with permission ideally) to see if they properly secured the solution you rely on.
- Consider vendor personnel exposure risks. If a vendor becomes part of your attack surface, so do some of their people who manage your account or have access to your data. For critical vendors, advise them to use personal data removal services for key personnel and implement enhanced security awareness training for staff handling your account.
Understand infrastructure managed by third parties that could affect your exposure.
- For example, if you outsource email to Office 365, an issue in O365 (like a vulnerability or a misconfig on your tenant) is part of your exposure. Keep track of those and ensure they're covered by your controls (like enabling O365 Secure Score improvements).
- If a vendor hosts a portal for you (like a payment processor with a page on their site for your transactions), that is an external asset from users' perspective. Coordinate with them on security (ensuring they patch, etc.) because an attacker might deface or compromise that portal and hurt your customers/trust.
- Supply chain software: if you deploy a vendor's software on your site (like a chat widget, analytics script), that vendor becomes part of your attack surface (Magecart attacks, etc.). Vet what you include - use subresource integrity for scripts if possible, or at least be aware of which external scripts are loading (CSP policies can restrict them).
- Map dependencies between third-party services in your ecosystem
- Identify potential OSINT collection points in vendor networks
- Conduct regular assessments of third-party attack surface
Secure shared workspaces and collaboration tools.
- Ensure access controls in those inter-company collaboration spaces are tight. Only intended people should be able to see data; an attacker breaching the partner's side shouldn't automatically see your files.
- Put guidelines: e.g., do not share secret keys or passwords in a shared Slack with a vendor - treat that channel as potentially externally accessible, because it's not fully under your control.
- If sharing large data sets, consider using secure transfer methods and expiring access after done.
- Treat shared channels as potentially external
Track what others publish about your organization.
- Press releases by partners might mention architecture or contracts. If a tech partner announces "We signed Client X and integrated with their Active Directory", well now attackers know you use Active Directory and who the partner is. You might not control that, but at least be aware so you can adjust (maybe ensure AD externally is locked tight, etc.).
- Competitors sometimes inadvertently reveal info (like comparing to you in an analysis - "We beat them because their system does X"). Track industry chatter to glean what might need securing.
- Dark web or forums: sometimes, supply chain info leaks (e.g., a hacker claims to have data from your law firm - if that surfaces, treat it as an incident).
- Be aware of unintentional disclosures by partners
- Monitor case studies and customer testimonials published by vendors
- Review conference presentations where vendors might reference your organization
- Establish disclosure guidelines with key business partners
- Create an approval process for any partner references to your organization
- Implement notification requirements for vendors regarding breach disclosures
Apply least privilege and verification to third-party integrations.
- If a vendor has VPN into your network, segment that access strictly. Many breaches occurred by attacker going through a smaller partner with weaker security into a big company (Target breach via HVAC contractor).
- Use separate accounts/keys for third-party integrations with limited scope. For example, if you give a marketing agency an account to your web CMS, don't make it an admin if they just need editor rights.
- Audit third-party accounts regularly - remove any that are no longer needed.
- Monitor third-party activity for unusual patterns - unusual activity could signal compromise of the partner.
- Verify all third-party actions regardless of trust level
FA3.SC5 Defense Against Automated OSINT Collection
Implement countermeasures against automated tools and techniques used for organizational reconnaissance.
Implement technical controls to prevent automated data harvesting from organization websites.
- Deploy CAPTCHA or other human verification on sensitive pages
- Implement rate limiting to prevent mass data collection
- Use JavaScript-based content rendering to deter basic scrapers
- Consider legal measures such as Terms of Service prohibitions
- Monitor for unusual traffic patterns indicating scraping activity
Defend against sophisticated AI-powered OSINT gathering techniques.
- Monitor for AI-driven reconnaissance patterns
- Implement content policies that prevent automated correlation
- Limit information that could be used for training AI models
- Create awareness about AI capabilities in OSINT collection
- Develop honeypots specifically designed to detect AI reconnaissance
Secure APIs against automated data harvesting.
- Implement robust API authentication and authorization
- Use API keys with appropriate rate limits
- Log and monitor API usage for suspicious patterns
- Limit data returned in API responses to minimum necessary
- Consider implementing OAuth 2.0 with strict scopes
Manage how information flows between systems to prevent automated collection.
- Implement data loss prevention to detect unusual data transfers
- Create segmentation between internal and external systems
- Control directory information exposure through federated services
- Encrypt sensitive data in transit between systems
- Implement least privilege access for information sharing
FA4 Executive Protection
Description
Executive Protection in the context of OSINT defense refers to safeguarding the digital (and to some extent physical) security of an organization’s high-profile personnel (executives, board members, public-facing figures) who are prime targets for information gathering and attacks. This includes protecting their personal data, social media, communications, and educating them and their families. It goes beyond typical corporate controls because executives often blur personal and professional spheres, and attackers exploit that. This focus area aligns with Identify (identify exec-specific risks), Protect (various protections for execs’ data and accounts), and Detect/Respond (monitor threats against them specifically). It also touches on privacy and personal security domains not usually fully covered by standard IT security frameworks, hence addressing it separately.
Business Rationale
Business owners and executives carry disproportionate risk. They have access to the most sensitive info, can authorize large transactions, and their public status makes them targets for hackers, fraudsters, and even nation-state espionage. An attack on an executive (like email compromise or doxing) can lead directly to a major breach or reputational crisis. Also, executives often have prominent digital footprints (press releases, social media mentions, etc., sometimes maintained by PR) which require special attention. Protecting them is not just about the individual’s safety, but the company’s continuity and reputation. For mid-size companies, the “executive” might just be the owner/founder - whose personal accounts could be a way into company systems (especially in SMBs where personal and business IT might mix). In larger enterprises, a compromised CEO or CTO could undermine all other security (attackers love to phish lower staff from the CEO’s account). Moreover, executives have more personal info online (30% more on average) and thus greater exposure to targeted threats. Thus, a framework for OSINT defense must directly address executive protection to ensure holistic security. Additionally, demonstrating strong executive protection measures can reassure stakeholders (investors, partners) that leadership is secured and mindful of risks.
FA4.SC1 Executive Digital Footprint Management
Greatly limit and monitor the personal information about executives that is publicly accessible.
Conduct a thorough audit of each executive's public personal information.
- Compile what's out there: full name variations, home address (check property records sites), phone numbers, personal email addresses, social media profiles (active or dormant), family member names, education (year of graduation can give age), etc.
- Check people search sites and data broker reports. Confirm what data brokers have on them: many have surprisingly detailed profiles (as noted, exec profiles often list incomes, properties, relatives).
- Review past news articles or press releases that mention them - sometimes personal tidbits get shared ("John Doe, avid pilot and father of two, will lead the division…" - now attackers know hobbies and family details).
- Assess social media - even if their profiles are private, see what profile photo, bio, or cover image reveals. Check if others (family, friends) have public posts with them tagged or pictured.
- This audit gives a baseline of exposure points to address.
Systematically remove or suppress executives' info from public sources.
- Use automated opt-out services for data brokers to systematically remove executives personal information from people-search sites and commercial databases. Ensure this specifically covers all executives and is maintained over time because data brokers continuously repopulate their databases, making this an ongoing rather than one-time effort.
- If not using a service, assign staff or use open-source lists to manually opt-out from major sites: Whitepages premium, Spokeo, Intelius, Radaris, etc. Then verify their profiles are gone or reduced.
- For public databases that don't remove info (like certain government records), consider alternatives: e.g., can they use a business address instead of home for registrations? Some execs set up PO boxes or use corporate HQ for mailing addresses to avoid exposing home addresses.
- Encourage execs to use privacy-protective practices personally: for instance, when buying a home, perhaps use a trust or LLC name if appropriate, so their personal name isn't easily tied to an address (common practice in celebrity privacy).
- Check often for new data broker entries or new sites (this ties into continuous monitoring, but specifically for personal data reappearing).
- Consider establishing dedicated privacy resources for ongoing opt-out management
- Create documentation for employees explaining the data broker removal process
Work with executives to sanitize their online presence.
- Ensure their social media profiles don't reveal sensitive personal data. For example, on LinkedIn, maybe they should hide their full birthday (to prevent someone using that for ID theft or account verification).
- Look at what connections or groups are public. Attackers can use an exec's connections to craft spear phishing ("I saw you know Person X…").
- Remove old accounts: find if they have accounts on platforms they no longer use (MySpace, old forums) and delete or lock them down. These can be resurrected by attackers if left abandoned.
- If the exec has a personal blog or website, make sure nothing sensitive is on it like detailed travel diaries or info that could be used maliciously.
- Google the executive's name and see what autocompletes and results show - if something negative or personal is trending, consider proactive PR or SEO to push it down (veers into reputation management).
Limit personal details in official company communications.
- Press releases about a new CFO hire don't need to include home city or family details (even if it seems harmless). Stick to professional achievements.
- On the corporate website's leadership page, consider whether to list things like exact university graduation years (could indicate age). Some is fine, but weigh what could be misused.
- If executives participate in public webinars or panels, caution about inadvertently sharing personal anecdotes that reveal more than intended. (e.g., "During my 6 AM jog at Central Park everyday…" - now someone knows where to find you).
- Photos of execs used publicly (like headshots in reports) should ideally not have location metadata and be taken in neutral settings (so as not to identify their home or specific office).
Extend protection to executives' families who could be targeted.
- Advise executives to educate their family members about privacy. For example, kids should be careful on social media not to overshare ("Heading to Dad's conference in Vegas!"). Emphasize that attackers may leverage children to target executives and employees, making family education critical for organizational security.
- Remove/minimize family references in public. Some companies list "Married with three children" in bios; that's optional and maybe better omitted.
- For those in high risk (controversial industries or high wealth), consider aliasing family online - e.g., using first name and last initial on social media rather than full name.
- Ensure home addresses are not easily found. If needed, engage physical security consultants for residential security which often includes digital intel aspects (like monitoring if home address gets posted on forums).
- Protect home addresses by using living trusts or LLCs for property ownership. Consult with legal and financial advisors to establish appropriate legal entities that obscure direct ownership connections in public property records, making it harder for attackers to identify executive residences through real estate databases.
- Establish alternative mailing addresses for sensitive documents. Set up private mailbox services, corporate addresses, or trusted third-party locations for receiving financial statements, legal documents, and other sensitive correspondence to prevent home addresses from appearing in various databases and delivery records.
- Provide data broker removal services for family members. Extend automated opt-out services to spouses and children of executives, systematically removing their personal information from people-search sites and commercial databases. Maintain this as an ongoing service since data brokers continuously repopulate their records.
- Coach family on the dangers of location tagging and geotagged photos. Train family members to disable automatic location services on social media platforms and cameras, and review posts before sharing to ensure they don't reveal current locations, routine patterns, or identifiable landmarks that could be used for targeting.
- Secure school directory information for children of executives. Work with schools to limit inclusion of executive children in published directories, yearbooks, and public school communications. Request that family information be kept confidential and establish protocols for handling media requests or public events involving executive families.
- Monitor children's device usage and online activities. Implement age-appropriate monitoring of children's internet usage, social media accounts, and gaming platforms where attackers might attempt to make contact or gather information about the executive's family.
- Ensure family devices don't compromise network security. Segregate family devices from corporate networks through separate home networks or VLANs. Apply security controls to family devices that connect to home networks where executives may also access corporate resources.
- Establish family incident response protocols. Create procedures for family members to report suspicious contact attempts, unusual online interactions, or potential targeting. Train family members to recognize and report social engineering attempts directed at them.
FA4.SC2 Secure Executive Communications and Devices
Implement heightened security for communication channels and devices used by executives.
Secure executive email accounts with enhanced measures.
- Ensure MFA is enabled on all executive email accounts (both corporate and personal). Encourage use of hardware security keys or at least app-based authenticators instead of SMS (execs are targets for SIM swapping).
- For personal email (like Gmail, Yahoo), help them enable additional features: account recovery info should be up-to-date (and not guessable answers), login alerts on new devices, possibly Google's Advanced Protection Program for high-risk users (which mandates security keys and limits third-party app access).
- Their corporate accounts might already be under company MFA, but also consider requiring password managers for them to avoid password reuse.
- If execs sometimes share passwords with assistants (common in small biz), discourage that practice - instead set up proper delegated access (like "send mail as" privileges for assistants, which can be audited, rather than giving out password).
- Email monitoring for VIPs, with permission, IT security can have enhanced logging or alerts on any unusual login or email forward rule creation on execs' accounts, since compromise would be so damaging.
Apply strong security to all executive devices and communication channels.
- Ensure all their devices are encrypted, with strong PINs/passwords (no 4-digit pins - encourage 6-digit or more, or biometric with good fallback).
- Install reliable security software on their devices (mobile threat defense on phones, anti-malware on laptops).
- Keep their devices updated; possibly have IT assist them regularly if they are not tech-savvy or too busy. Many high-profile hacks (Jeff Bezos phone hack via WhatsApp, etc.) exploited unpatched apps.
- For particularly high-risk individuals, consider special hardened devices (some execs use separate secure phones for sensitive comms).
- Prevent SIM Swap: Work with execs to add extra protections at their mobile carrier (a PIN on the account, or port freeze). This addresses attackers who try to social engineer phone companies to steal numbers (since many services rely on SMS 2FA).
- Provide VOIP telephony solutions like Microsoft Teams numbers that are resistant to SIM swap attacks
- Secure cloud-based admin accounts that manage VOIP numbers
- Consider privacy-focused alternatives like MySudo for essential communications
- Ensure proper backup configuration of communication tools with strong security for cloud accounts
- Educate executives about risks of SIM swap attacks and warning signs
- Implement security controls for home office environments
- Establish guidelines for securing remote work spaces from physical observation or eavesdropping
- Set and enforce limits on ad tracking and data collection: On company-managed devices, disable ad tracking features (iOS "Allow Apps to Request to Track" and Android "Opt out of Ads Personalization"), turn off Apple Intelligence & Siri data sharing, and disable analytics reporting to prevent apps, advertisers, and platform providers from collecting behavioral data, location patterns, usage information, and device analytics that could be exploited for OSINT targeting. This prevents the creation of detailed digital profiles that attackers could use to understand executive routines, travel patterns, business relationships, or device usage behaviors.
Use encrypted messaging for sensitive discussions.
- Provide executives with a secure messaging app (Signal, WhatsApp, or an enterprise secure comm tool) for discussing sensitive business if not on email. Ensure they know to use it especially when traveling or discussing confidential matters.
- For extremely sensitive communications (board discussions, M&A info), consider setting up a secure portal or encrypted email solution (like ProtonMail or enterprise S/MIME). If that's too heavy, at least ensure any attachments with highly sensitive info are password-protected or shared via secure links, not plain email.
- Train them on how to verify the identity of people on calls or messages (especially if using something like WhatsApp, which shows contact names that could be faked if someone got a hold of a phone - maybe not likely but caution).
- If they use video conferencing (Zoom/Teams) for important meetings, those should be password protected meetings with waiting room features to avoid uninvited guests (Zoom bombing an exec meeting can yield OSINT or embarrassment).
Secure executive devices that bridge personal and work use.
- Use MDM (Mobile Device Management) solutions on any device that accesses corporate data, even if it's their own. At least use containerization for email (like Outlook app with corporate controls).
- For BYOD devices that execs use, have IT at least do a security check or install necessary controls, with exec's consent. Emphasize it's to protect them and the company.
- Provide company-secured alternatives: e.g., if an exec is using a home PC for work, maybe provide them a secure laptop to use at home instead.
- Ensure remote access tools (VPN, etc.) used by exec are configured with MFA and limited access to needed resources.
- Possibly supply privacy screens or other physical security tools for their devices if they travel often (to prevent shoulder-surfing or camera spying).
Include executives in security testing and drills.
- They should be testable just like other employees, albeit with perhaps tailored scenarios. This keeps them on their toes and signals that they're not above the policies.
- Ensure they understand it's not to inconvenience them but to validate their protection; share results privately with them and coach as needed.
- If an executive consistently falls for simulations, that is a risk to address delicately - possibly more one-on-one training or adjusting controls to compensate (like maybe they get a stricter email filter or additional monitoring).
- Also consider physical social engineering tests if relevant (like someone trying to access the exec's office). While more physical, it's part of integrated security to ensure their whole environment is safe.
FA4.SC3 Threat Monitoring and Incident Response for Executives
Continuously monitor for threats targeting executives, and have a defined response plan for incidents.
Monitor for threats specifically targeting leadership.
- Set up alerts for your executives' names on dark web, paste sites, and social media. If credentials or personal info show up (like someone selling "CEO of X's email password" or posting their credit card number), you need to know ASAP.
- Monitor hacker forums or communities for mentions of targeting your leadership. Sometimes hacktivists or others explicitly threaten executives or discuss them.
- Use services or Google Alerts for mentions of "[Exec Name] leak", "[Exec Name] filetype:pdf" etc., that might indicate leaked documents or personal data.
- Leverage social media listening tools to gauge if an executive is receiving unusual attention or harassment online (spikes in negative mentions could hint at a campaign).
- Keep an eye on public breach data for their personal emails (like if their personal Gmail shows up in a combo list, ensure they know to change stuff).
Detect fake profiles and impersonation attempts.
- Monitor for fake profiles: as noted, search LinkedIn, Twitter, etc. for accounts pretending to be the executive or a slight variation (especially if they normally don't have an account on a platform). Immediately report those for removal.
- Keep tabs on domains that could be used to impersonate exec or company (typosquats that include exec name perhaps).
- Watch out for phishing attempts where exec's identity is used. If employees report an email from "CEO" that was fake, treat it as a significant event, not just routine phishing, since someone is targeting via the exec's persona.
- Inform execs if you discover impersonations or scams using their name, even if it doesn't directly impact them yet. They may get weird calls or messages from confused people as a result (like scammers using their name with customers).
- Law enforcement relationships: consider liaison with authorities for serious impersonation/fraud cases (like if someone continually impersonates a CEO on social to pump stock or something, that might be SEC or FBI relevant).
Respond to exposure of executive personal information.
- Have an immediate action plan: this might involve contacting platform moderators to remove content (Twitter, Reddit, etc. often will remove doxing content when flagged).
- Assist the executive in securing accounts if, for example, their personal email or social got compromised in the course of harassment.
- If threats are involved (e.g., explicit threats to harm), escalate to law enforcement quickly. Maintain logs of threatening messages.
- Public relations plan: coordinate with corporate communications on how to handle any public narrative. For instance, if false information is spread about the exec, PR might need to issue a statement.
- Legal avenues: cease and desist letters to harassers if identified, or restraining orders in extreme cases. Companies sometimes quietly pursue this to protect their people.
Practice response to executive-targeted incidents.
- Example scenario: "The CEO's email is compromised and the attacker sent out a fake press release. Go." Walk through communications, technical containment, legal. This prepares teams and execs on how to respond calmly.
- Another scenario: "Our CEO is doxxed by hacktivists during a controversy - personal address and family details posted." Practice who contacts who, do we involve law enforcement, what is messaging to employees (they'll worry about their own data too), does CEO need temporary relocation, etc.
- These exercises highlight gaps (maybe you realize you lack a contact at a social media company to fast-track removals - you might then establish one preemptively).
- Practice cross-functional coordination
Prepare for recovery after executive-related incidents.
- For instance, if CEO's email was hacked and used maliciously, after securing it, consider sending out verification emails to recipients who might've gotten the false ones, to clarify any confusion (avoiding future social engineering ripple effects).
- If an executive's device is stolen, ensure remote wipe and then decide if any corporate credentials might be at risk, forcing password resets or tokens reissued.
- If an exec's personal social media posted something unauthorized (like a hacker posting an outrageous statement), help them recover the account and issue clarifications.
- Internally, consider if the exec needs to be temporarily removed from some access until things are secured (for example, if you suspect an attacker might have some of their credentials, maybe temporarily lock their accounts until sure).
- Also, plan for succession in crisis: If an exec is out of pocket due to an incident (say law enforcement takes their devices for evidence after a personal breach), have a way to continue business (someone else authorized for approvals, etc.). This crosses into business continuity.
FA4.SC4 Executive and High-Profile Personnel Safeguards
Provide additional protective measures for executives or other high-profile personnel who are prime targets for social engineering due to their influence or access.
Conduct one-on-one or small-group training with executives about targeted social engineering.
- Explain specific risks like Business Email Compromise
- Encourage leadership by example in security practices
- Warn about personal sphere attacks
- Discuss deepfake possibilities and verification methods
Limit how executives will issue critical instructions.
- Establish specific channels for official requests
- Define communication protocols during travel
- Implement additional protection for executive accounts
- Consider digital signatures for authentication
Prevent creation of fake profiles or accounts impersonating executives.
- Reserve executives' likely usernames on major platforms
- Monitor for impersonation accounts
- Publish official channels to help verify authenticity
- Take down fraudulent accounts quickly
Train support personnel who often handle communication on behalf of executives.
- Include assistants in security training
- Implement verification for requests to assistants
- Establish notification policies for executive unavailability
- Create verification protocols for unusual requests
Manage information shared during public appearances.
- Brief executives before public speaking
- Adjust security monitoring after major public events
- Be aware of personal information that becomes public
- Train on handling media and public questions
FA4.SC5 Physical Location Privacy and Security
Protect executives' physical location information and enhance security measures at locations frequented by executives.
Implement measures to obscure and protect home addresses and physical locations of executives.
- Use living trusts, LLCs, or nominees for property ownership
- Implement mail forwarding or private mailbox services
- Ensure property records don't link directly to executives
- Consider CCTV and security systems with remote monitoring
- Remove executive home addresses from voter registration records where legally permitted
- Establish protocols for package deliveries to avoid home address exposure
Establish protocols for secure executive travel and commuting.
- Use private transportation services that emphasize security and privacy
- Avoid routine patterns and predictable schedules
- Establish travel reservation procedures that minimize personal information exposure
- Consider temporary devices or communication methods for high-risk travel
- Disable location services on devices when not needed
- Create guidelines for secure remote work practices when traveling
Prevent inadvertent disclosure of executive locations through metadata and digital footprints.
- Disable geotagging on all executive devices and photo applications
- Review and confirm location privacy settings across all social accounts
- Train executives to be aware of background identifiers in photos/videos
- Implement tools to strip location metadata from shared files
- Avoid location check-ins or location-based services on personal accounts
- Disable location history tracking on devices and accounts
Secure home IoT devices and smart systems that could reveal occupancy or personal information.
- Audit all home IoT devices and smart systems for security vulnerabilities
- Use separate networks for smart home devices
- Implement strong authentication for all connected home systems
- Disable unnecessary features that might collect or transmit location data
- Consider privacy implications of voice assistants and smart speakers
- Secure home automation systems to prevent occupancy pattern analysis
Establish protocols for executive public appearances to reduce OSINT exploitation opportunities.
- Limit pre-announcements of executive attendance at events
- Control photography and recording during events
- Establish social media policies for event attendance
- Consider security personnel presence at high-profile events
- Brief executives on physical OSINT risks before public engagements
- Prepare contingencies for unexpected security situations at events
FA4.SC6 Executive Financial Privacy
Protect executives' financial information and transactions from OSINT collection and exploitation.
Enhance security measures for executive financial accounts and transactions.
- Use virtual card numbers for online transactions where available
- Establish dedicated accounts for public-facing activities
- Implement maximum security options with financial institutions
- Consider enhanced verification procedures for significant transactions
- Use secure communication channels for discussing financial matters
Minimize exposure of executive financial information in public records.
- Review and address public-facing financial declarations and records
- Use legal entities to obscure direct ownership connections
- Consider jurisdictional options for financial privacy
- Implement enhanced security freezes with credit bureaus
- Monitor business registrations and licensing information
Secure physical and digital financial communications.
- Use secure mail handling for financial documents
- Establish dedicated secure channels for financial advisors
- Implement end-to-end encryption for financial communications
- Develop procedures for secure document disposal
- Create protocols for verifying financial communication authenticity
Enhance privacy of digital payments and online financial activities.
- Use enhanced authentication for payment applications
- Consider dedicated devices for financial transactions
- Implement privacy-focused browser practices for financial sites
- Avoid linking personal information to payment systems
- Regularly audit online financial footprint and subscriptions
FA4.SC7 Disinformation Defense and Reputation Management
Protect executives and the organization from disinformation campaigns and reputation attacks.
Continuously monitor for unauthorized use of executive identities and images.
- Implement reverse image search monitoring for executive photos
- Monitor for deepfake content featuring executives
- Track executive name mentions across various platforms
- Set up alerts for unauthorized use of executive quotes or statements
- Develop verification protocols for official executive communications
Register domains and social media handles to prevent squatting and impersonation.
- Secure variations of executive names as domains
- Register common misspellings and typosquatting domains
- Reserve key social media handles even if not actively used
- Implement regular monitoring of new domain registrations
- Consider registering domains for future executives or board members
Develop plans for responding to false information campaigns targeting executives.
- Create executive-specific crisis communication plans
- Establish verification standards for executive content
- Develop relationships with platforms for expedited content removal
- Train communications team on disinformation response
- Prepare templates for common disinformation scenarios
Protect and manage the use of executive images and likeness.
- Maintain controlled repository of approved executive images
- Implement watermarking or tracking for official photos
- Create usage guidelines for executive images
- Consider legal protections for executive likeness
- Monitor for unauthorized manipulation of official images
FA5 Continuous Monitoring and Response
Description
Continuous Monitoring and Response refers to the ongoing activities to detect OSINT-related threats or exposures as they arise, and to respond to them in a timely manner. Unlike one-time assessments or periodic reviews, this focus area emphasizes a 24/7/365 vigilance and an agile response mechanism. It leverages security monitoring, threat intelligence, and incident response processes. In NIST CSF terms, this aligns strongly with Detect (DE.CM - continuous monitoring) and Respond/Recover functions. It ensures the framework remains effective against evolving threats by constantly watching the public sphere for new relevant information and handling incidents when they occur.
Business Rationale
The OSINT landscape and threat environment are continuously changing. A company might do everything right today, but tomorrow a new breach, a new leak, or a new attacker tactic could put it at risk. For example, an employee might unknowingly post something sensitive tomorrow that wasn’t there when the initial footprint reduction was done, or a new data dump might include some of your data. Continuous monitoring provides early warning, allowing a business to react before small issues become crises. It also helps maintain the hard-won gains of footprint reduction by catching any regressions (like a misconfigured setting that accidentally made something public). From a business standpoint, this focus area is crucial for resilience: it’s not a matter of if, but when, an OSINT exposure or social engineering attempt will happen. Being prepared to spot and respond swiftly can mean the difference between a minor contained incident and a headline-making breach. Regulators and standards (like ISO, SOC2) also increasingly expect continuous security monitoring as part of due diligence. Furthermore, for executives and brand protection (previous focus), continuous monitoring is the only way to guard their reputation in real-time. Overall, this focus area ensures the organization remains adaptive and responsive, reinforcing that security is a process, not a destination.
FA5.SC1 OSINT Threat Intelligence and Monitoring
Continuously gather and analyze intelligence from open sources to identify potential threats or exposures related to the organization.
Monitor for data breaches and dark web leaks.
- Utilize services or feeds (HaveIBeenPwned API for domain, Dark web monitoring services) to get alerts if any company email addresses or credentials appear in new breaches.
- When a breach at another company is announced, quickly assess if any of your accounts could be affected (e.g., employees reusing passwords on that breached service - if you detect, enforce password resets).
- Monitor dark web forums/marketplaces for your company name, product names, executive names. Attackers sometimes sell initial access specifically naming the company, or dump database segments.
- Use Tor or dark web monitoring tools (careful to follow legal guidelines) to search for mentions of your domains, IP ranges, etc. Some threat intel vendors specialize in this if you have budget.
Track mentions and data across social media and code sites.
- Set Google Alerts (or more advanced tools) for keywords like " confidential", " leak", key project code names, etc. Also for exec names paired with certain words (e.g., " hack").
- Monitor sites like Pastebin, GitHub Gist, etc., for dumps containing your company email domain or other unique strings (there are specialized tools like Pastebin scraping services).
- Follow social media chatter around your brand. Unusual posts by disgruntled employees or others might hint at a leak ("I could expose so much about …"). Those need proactive address (contact HR/legal).
- If you have products or customer data, monitor file-sharing and torrent sites as well, in case someone posts a stolen data set labeled with your name.
- Use brand protection services that flag fraudulent websites or apps impersonating your brand (phishing sites with your logo, malicious mobile apps named after your product, etc.).
Continuously scan external assets for changes.
- This overlaps with vulnerability management but is part of monitoring to catch things like a new port opening or a certificate change that wasn't planned.
- Some ASM tools will alert in near real-time if a new subdomain appears or an existing one changes IP/hosting (could indicate compromise or a new unapproved deploy).
- Also monitor configuration drift: e.g., using cloud security posture tools that alert if a previously private S3 bucket becomes public.
- Tie this to a dashboard or alerting system in your Security Operations Center (SOC) if you have one.
Participate in information sharing communities.
- If your industry has an ISAC (Information Sharing and Analysis Center), subscribe to see if any threats are hitting peers that could come your way.
- Government or law enforcement alerts (like CISA alerts) sometimes highlight active social engineering campaigns or new OSINT tool use by adversaries.
- Keep up with OSINT research community - new tools that could be used against you (for example, if a new tool automates scraping LinkedIn in clever ways, know about it).
- Subscribe to feeds about domain registrations similar to yours (some services send daily reports of lookalike domains).
- Maintain a relationship with external threat intel vendors if possible; they can provide context, e.g., "We've observed chatter about targeting companies in your sector for social engineering".
Integrate OSINT data with security monitoring tools.
- If you get data from breach monitoring (like a list of compromised hashes), feed it into internal systems to detect if those credentials are used (some SIEM can ingest and compare to authentication logs).
- Log access to any "honeypot" info you set up (as mentioned earlier, if you have honeytokens that phone home). Alerts on those triggers indicate likely reconnaissance or intrusion.
- Analyze inbound traffic to web services for OSINT-like patterns - e.g., someone scraping your site intensively (maybe preparatory recon). Rate-limit or block scrapers if not legitimate (though need to differentiate from search engines).
- Keep logs of queries/hits on your public bug bounty or disclosure channels, if any - weird requests might indicate people probing for leaks ("can I have your employee list?" type emails to support).
- Evaluate anomaly detection solutions that might highlight patterns indicating an OSINT-driven attack in progress (like multiple employees receiving personalized phishing - which suggests targeted recon preceded it).
FA5.SC2 Incident Response and Adaptation
Have a well-defined process to respond to any incidents or discoveries from monitoring, and adapt security controls based on lessons learned.
Develop specific playbooks for likely OSINT-related incident scenarios.
- For example: "Public Data Leak Detected" (like discovering a confidential document on Pastebin) - steps might include identifying source, getting it taken down, invalidating any credentials in it, internal comms to reinforce policy that led to leak.
- "Phishing Campaign Underway" - steps to gather phishing samples, block sender/domains, push out awareness message, possibly take down phishing site (coordinating with the web host or using services that do).
- "Impersonation Scam" (like fake invoices to customers or fake social media profiles as discussed) - who will contact customers or social media to mitigate, how to inform stakeholders.
- "Executive Doxing/Threat" - pulling from Exec Protection, steps to protect, involve authorities, etc.
- "Third-Party Breach affecting us" - e.g., vendor X was breached and our data possibly spilled - steps to coordinate, maybe cut connectivity until sure, notify if necessary.
- These playbooks should list roles (who from IT, PR, legal, etc.) and contact info for outside parties (law enforcement, platforms, etc.).
Implement mechanisms to quickly mitigate discovered exposures.
- For online content: know how to file abuse reports to different platforms (maybe even have contacts or an account with a service that does global takedowns).
- For malicious domains or apps: use services like Google Safe Browsing or Microsoft's reporting to get them flagged as dangerous (makes browsers warn users).
- If a domain impersonating you arises, possibly engage domain registrars or use legal channels (like trademark infringement notices) to claim or suspend it.
- If credentials are leaked, implement forced password resets and multi-factor on those accounts immediately (maybe automatically if integrated).
- For any data leak, initiate containment: e.g., if it's a code leak with keys, instantly disable those keys.
- Test these processes occasionally to ensure you can react fast (like simulate needing to remove something from Pastebin - do you know the steps and how long it takes?).
Develop clear communication procedures for incidents.
- Have templates ready for internal communications (to employees - e.g., "We detected phishing, don't trust X").
- If customer data is involved in a leak, have draft customer notification letters (taking into account legal requirements like GDPR 72-hour breach notifications, if applicable).
- For executive incidents, as noted, coordinate with PR for any public statements or media inquiries.
- Ensure the incident response team knows when to escalate to senior management or incident management team - OSINT incidents can escalate quickly (e.g., if trending on Twitter, the company needs to respond publicly maybe).
- Keep logs of all decisions and communications for after-action review and for any legal follow-ups.
Feed incident learnings back into security controls.
- Perform a post-incident review that asks: how did our OSINT defenses fare? Was the issue something we should have caught or prevented? If yes, why didn't we? Then adjust.
- If a new type of phishing hook was effective, incorporate that scenario into the training content and phishing simulations going forward.
- If a data leak occurred because a process wasn't followed (e.g., an S3 bucket was made public), revise the process or add an automated control to prevent it (like requiring security review in change management).
- Adjust monitoring rules based on what was missed - for instance, if an incident was detected by an employee report but not by the SOC, improve the correlation rules or intelligence sources so the SOC catches it next time.
- Update policies if needed. Maybe an incident reveals ambiguity in responsibility (who should have approved a post or responded to a report); clarify that in the relevant policy.
- Share sanitized findings across the organization (and even with industry peers if appropriate) so everyone learns. This fosters a culture of continuous improvement and shows that the framework adapts to new threats.
Integrate OSINT defense with executive travel security planning.
- Conduct pre-travel OSINT sweeps for high-risk destinations
- Establish temporary communication protocols during travel
- Implement post-travel privacy cleanup procedures
- Brief executives on location-specific OSINT risks before travel
- Provide secure travel equipment and communication methods
- Create procedures for secure disposal of travel materials
FA5.SC3 Measurement and Metrics
Establish quantitative metrics to measure the effectiveness of OSINT defense activities and track improvements over time.
Develop a quantitative methodology to measure organizational OSINT exposure.
- Create a baseline OSINT exposure score for the organization
- Develop metrics for measuring digital footprint size and sensitivity
- Implement regular scoring of different organizational units
- Track exposure score changes over time
- Benchmark against industry peers where possible
Measure the performance and effectiveness of OSINT defense activities.
- Track remediation times for identified exposures: Measure mean time to remediation (MTTR) for different types of OSINT exposures, from discovery to complete resolution. Establish baseline metrics and track improvements over time. Include metrics for critical exposures (executive personal data, credentials) versus lower-priority items (general company information).
- Measure detection rates for planted canary data: Deploy honeytokens, canary profiles, and fake information across various platforms and measure how quickly they are accessed or referenced in social engineering attempts. Track the percentage of canary triggers that lead to successful threat detection and compare detection rates across different deployment strategies.
- Quantify reduction in sensitive data exposure: Establish baseline measurements of sensitive data discovered through OSINT tools and track percentage reductions over time. Measure specific categories such as employee personal information, technical infrastructure details, financial data, and executive information separately to identify program strengths and gaps.
- Calculate return on investment for OSINT defense activities: Measure costs of OSINT defense programs against prevented losses from blocked social engineering attempts, avoided data breaches, and reduced incident response costs. Include metrics for time saved through early threat detection and prevention of more costly security incidents.
- Develop metrics for frequency and impact of OSINT-related incidents: Track the number of OSINT-based social engineering attempts, successful compromises, and near-misses. Measure the business impact of prevented and successful attacks, including financial losses, operational disruption, and reputational damage. Include trends analysis to identify seasonal patterns or campaign-based attacks.
- Monitor email security effectiveness: Track the volume of quarantined emails with social engineering indicators before and after implementing ODSF controls. Measure reductions in sophisticated phishing attempts that reference specific organizational or personal details, indicating attackers have less OSINT to leverage in their campaigns.
Establish measurable KPIs for OSINT defense program success.
- Define target metrics for exposure reduction
- Set goals for time-to-detection of new exposures
- Create KPIs for employee awareness and behavior
- Develop metrics for third-party risk reduction
- Establish executive-specific protection metrics
Create effective reporting mechanisms for OSINT defense metrics.
- Develop executive dashboards for OSINT risk visibility
- Create trend visualizations for exposure over time
- Implement automated reporting on key metrics
- Provide risk-based scoring for different types of exposures
- Develop comparison metrics against industry standards
FA5.SC4 OSINT Deception Strategy
Implement active deception tactics to confuse adversaries and detect reconnaissance activities.
Strategically place false or misleading information to detect and misdirect adversaries.
- Create fictitious project names and data that would attract attention
- Develop detailed but false information that appears valuable
- Deploy unique identifiers within false data for attribution
- Establish monitoring mechanisms for honey information access
- Update and rotate deceptive content regularly
Create signal-to-noise challenges for adversaries attempting OSINT collection.
- Implement deliberate noise in non-sensitive public data
- Create plausible but misleading information streams
- Use intentional ambiguity in public-facing content
- Deploy contradictory information across different channels
- Design noise patterns that preserve business functionality
Deploy decoy systems and services to detect and analyze OSINT collection.
- Create honeypot systems that appear to be production assets
- Deploy deceptive DNS entries and subdomains
- Establish fake API endpoints with monitoring
- Develop shadow IT systems that appear vulnerable
- Implement alerts for interaction with deceptive infrastructure
Develop plans for actively engaging with identified adversaries conducting reconnaissance.
- Create procedures for controlled interaction with adversaries
- Establish thresholds for active counter-intelligence measures
- Develop escalation paths based on adversary behavior
- Design playbooks for different types of adversary engagement
- Implement attribution mechanisms in engagement strategies
FA5.SC5 Internal OSINT Defense
Protect against internal reconnaissance and limit the organization's vulnerability to insider threats leveraging OSINT techniques.
Implement need-to-know access controls and information boundaries.
- Establish clear data classification guidelines
- Implement technical controls for sensitive information access
- Create information barriers between departments where appropriate
- Develop policies for internal information sharing
- Monitor for unusual internal information access patterns
Implement measures to detect internal OSINT collection activities.
- Monitor for unusual directory or resource enumeration
- Deploy internal honeytokens to detect unauthorized collection
- Establish baselines for normal information access patterns
- Create alerting for potential internal reconnaissance
- Implement user behavior analytics for detecting abnormal search patterns
Secure internal project names and codenames from external disclosure.
- Develop procedures for assigning non-descriptive project names
- Create guidelines for discussing internal projects externally
- Implement technical controls to prevent project name leakage
- Monitor for project codenames appearing in external sources
- Create awareness about the risks of revealing internal project details
Limit the exposure of detailed organizational structure information.
- Minimize public disclosure of detailed org charts
- Protect internal reporting structures from external visibility
- Create guidelines for job descriptions and titles
- Implement technical controls for directory information access
- Monitor for leakage of organizational structure details
FA5.SC6 Regulatory and Compliance Alignment
Ensure OSINT defense activities align with relevant regulations and compliance requirements.
Align OSINT defense with data protection regulations like GDPR, CCPA, and others.
- Map OSINT defense activities to specific regulatory requirements
- Implement data subject rights handling for OSINT-collected information
- Create documentation connecting OSINT controls to compliance obligations
- Develop procedures for regulatory reporting of OSINT-related incidents
- Establish legal review processes for OSINT defense activities
Address vertical-specific regulatory requirements in OSINT defense.
- Identify industry-specific information protection requirements
- Implement controls for regulated data that might appear in OSINT
- Create documentation for regulatory examinations and audits
- Develop mapping between industry standards and OSINT controls
- Establish regulatory monitoring for changes affecting OSINT defense
Align OSINT defense with international privacy standards and requirements.
- Map OSINT controls to ISO/IEC 27701 requirements
- Implement cross-border data protection measures
- Create procedures for handling international OSINT incidents
- Develop awareness about regional privacy expectations
- Establish multi-jurisdictional OSINT defense approaches
Maintain appropriate records of OSINT defense activities for compliance purposes.
- Create auditable records of OSINT monitoring and remediation
- Implement evidence preservation procedures for OSINT incidents
- Develop documentation standards for regulatory inquiries
- Establish retention policies for OSINT defense records
- Create compliance reporting templates for OSINT activities
FA5.SC7 Cross-Platform Identity Linkage Prevention
Prevent correlation and linkage of organizational and employee identities across different platforms and services.
Establish segmented online identities to prevent cross-platform correlation.
- Create separate personas for different organizational functions
- Implement technical separation between personal and professional accounts
- Develop guidelines for consistent identity separation
- Provide tools for managing multiple digital identities
- Create awareness about identity correlation risks
Minimize recognizable patterns that enable identity correlation.
- Analyze and eliminate consistent username patterns across platforms
- Identify and address writing style and communication patterns
- Implement varied registration information for different services
- Create awareness about behavioral fingerprinting techniques
- Develop guidelines for reducing cross-platform identifiability
Deploy technical controls to prevent automated identity correlation.
- Implement browser compartmentalization for different identities
- Use VPNs or other IP diversification methods for sensitive activities
- Develop procedures for secure identity switching
- Create awareness about browser fingerprinting risks
- Establish technical controls for preventing cross-site tracking
Detect attempts to correlate organizational identities across platforms.
- Implement monitoring for identity correlation attempts
- Create canary identities to detect mapping activities
- Develop alerting for unexpected identity connections
- Establish procedures for responding to identified correlation attempts
- Create awareness about signs of identity mapping activities
FA5.SC8 OSINT Training Program
Develop and maintain a comprehensive education program on OSINT risks and defensive practices.
Tailor OSINT defense training to different organizational roles and responsibilities.
- Develop specific OSINT training for executive, technical, and general staff
- Create specialized modules for high-risk roles
- Implement progressive training based on exposure and responsibility
- Establish role-transition training for changing positions
- Develop awareness materials targeted to specific job functions
Provide specialized OSINT defensive training for technical personnel.
- Create developer-specific training on code repository security
- Implement IT staff training on infrastructure exposure
- Develop specialized training for DevOps and cloud teams
- Establish advanced training for security personnel
- Create awareness about technical information leakage vectors
Provide targeted education for executives on high-profile OSINT threats.
- Develop executive-specific modules on personal exposure risks
- Create awareness about family and household OSINT vulnerabilities
- Implement specialized training on executive targeting techniques
- Establish regular updates on emerging executive threats
- Develop one-on-one coaching for highly targeted individuals
Establish internal certification programs for OSINT defense knowledge.
- Create basic and advanced OSINT defense certification tracks
- Implement competency verification for critical roles
- Develop practical exercises to demonstrate OSINT defense skills
- Establish recertification requirements for changing threats
- Create recognition programs for OSINT defense champions