Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

11/17/2016
12:00 PM
Sean Martin
Sean Martin
Slideshows
Connect Directly
LinkedIn
RSS
E-Mail

8 Public Sources Holding 'Private' Information

Personal information used for nefarious purposes can be found all over the web - from genealogy sites to public records and social media.
2 of 9

Source: Your Company Website

The most likely place an adversary will begin to look is at your own company website.

Adam Meyer, chief security officer of SurfWatch Labs, explains that while there are plenty of sites that criminals can use to can show detailed information about domains, IP addresses and effective attack vectors to try, the best way for someone to find information about a particular target is by getting it directly from the source: you.

Most corporate or company websites are a treasure trove of information attackers can use to target a specific organization, says Meyer. Names of VIPs, email addresses of various people in the company, photographs, Linkedin profile links....the list goes on. And that's the easy, obvious stuff.

Meyer reminds us that, if your company is hosting any PDFs, Word documents, Excel spreadsheets, and PowerPoint presentations for people to download, its important to remove potential metadata from those documents that could potentially contain additional names, email addresses, usernames, or software versions of the program used to create it. All of that information can be leveraged for attacks, such as spearphishing.

Some pretty simple Google searches (just type site:yourpublicsite.com filetype:pdf into the Google search box) can reveal much more information that you may not have been aware you were leaking, Meyer adds.

Image Source: SurfWatch Labs

2 of 9
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.