Axur provides a comprehensive set of solutions to safeguard companies against various types of data leaks, including the “Other Sensitive Data” offering. In this article, we will explore how this solution detects sensitive information related to your brand or domain without analyzing the specific content of the documents.
What Does the Other Sensitive Data Offering Do?
The Other Sensitive Data offering identifies sensitive content affecting clients by conducting searches in files, buckets, and boards where mentions of your brand or domain exist. This includes:
Exposed internal documents on sharing platforms: Examples include platforms like Scribd and 4Shared, where documents related to your brand may be inadvertently exposed.
Internal information on public boards: The solution checks platforms like Trello for publicly available internal information.
Financial documents and other sensitive data: Detection does not involve content analysis, focusing exclusively on brand mentions as the main detection feature.
Exposure of information in S3 Buckets: This encompasses services such as Amazon AWS, Azure Blobs, Digital Ocean Spaces, Google API, Windows Net, and others.
A leak of sensitive information on social media: Monitoring threats on social media platforms.
What Doesn't the Other Sensitive Data Offering Do?
Unauthorized content distribution: The solution is not intended to track the unauthorized distribution of images, audio, or videos.
Multimedia content analysis: It does not analyze images, audio, or videos.
Threats of leaks without content: It focuses on detecting brand mentions in documents rather than content-less threats.
Sources and Collectors
Axur uses a variety of sources and collectors to provide broad and accurate coverage:
Standard: Bitbucket, Pastebin, Google-Web Search Collector, GitHub, Grayhatwarfare, Amazon AWS, Azure Blobs, Scribd.
Attention!
The following collectors are not automatically enabled after registering on the platform: Bitbucket, Github, Grayhatwarfare, Scribd, Postman, Twitter.
The other collectors (Pastebin, Google Web Search, and Doceru) are enabled by default.
More details about our exclusive sources
GitHub: This collector allows that our client monitor specific strings that might have a high relevance. For example, if a customer wants to monitor a specific API key in GitHub, he can through Search bots create a Bot to monitor it.
As for this moment, it is not possible to create regex searches in this source.
Grayhat Warfare: This collector allows that our client monitor a specific filename in a bucket that might suit a specific need.
Grayhat usually updates it's database every 45 days so it is expected that this source detections show peaks of detection in certain weeks. It can be configured through search bots.
Scribd: This collector focuses on finding documents that contain on its title or body a mention of desired information. Through Search bots we are able to search for any sort of textual information we want. For example, a customer needs to monitor if a certain campaign slogan was shared without previous approval.
Pastebin: This collector is slightly different from other collectors we have. We do not request Pastebin for a specific paste in our requests, but we receive every X time a batch of pastes uploaded to the service. We then store it internally and only then we inspect it. Collections by standard are executed every 4 hours.
Whenever a new Bot is created for this source, the respective collection, on its first run, will inspect all pastes added to our paste database in the last 30 days. The following That being said, it is important that we put a lot of attention when creating, because a misconfigured Bot can generate a great volume of results.Bitbucket: This collector only searches for mentions in repository titles. Right now, it is not possible to search for mentions in code or other fields. Therefore, it is recommended that before creating a Search bot we test our search in the following https://bitbucket.org/repo/all?name=.
Postman: This collector searches for content in Postman, such as Workspaces, Collections, Requests, and Teams. It's important to set up the BOT using single terms. If you're searching for a compound word, domain, URL, or any term that includes spaces or special characters, it is recommended to include these terms in a Library and enable the "page content" filter in the Advanced Settings.
Manual Creation of Tickets in the Other Sensitive Data Offering
If there is a need to manually create a ticket in the platform for reporting Other Sensitive Data, the process is similar to other offerings and can be consulted in the “Manual Addition of Tickets” article.
Attention! Before creating a ticket, search the platform to identify possible tickets already created for the case. For more information, consult the “Manual Ticket Search” article.
Access the Data Leakage section.
2. On the right corner, click on the “+ Add Ticket” button.
Select the asset related to the fraud.
Choose the ticket type “Other Sensitive Data.”
Insert the URL. If there is more than one URL, select the “Create more than one ticket” option.
Click on the “+ Add.”
You have successfully created the Other Sensitive Data ticket. \o/
Axur is constantly enhancing its collectors to provide effective protection against data leaks. Protect your brand and sensitive data with Axur.
If you have any questions, feel free to reach out at [email protected] 😊