This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
leak_search [2024/11/25 13:38] kaduuwikiadmin |
leak_search [2025/03/06 13:48] (current) kaduuwikiadmin [How up to date is the data?] |
||
---|---|---|---|
Line 11: | Line 11: | ||
Monitoring whether your organization’s name appears in Dark Web forums, Onion-, I2P and paste sites can help you detect potential insider threats, enabling you to prevent data leaks and other incidents that may cause damage to your organization. Dark Web monitoring involves actively searching and tracking the Dark Web for information about your organization, | Monitoring whether your organization’s name appears in Dark Web forums, Onion-, I2P and paste sites can help you detect potential insider threats, enabling you to prevent data leaks and other incidents that may cause damage to your organization. Dark Web monitoring involves actively searching and tracking the Dark Web for information about your organization, | ||
- | ==== How up to date is the data? ==== | + | ==== How do we find the leaks? ==== |
+ | |||
+ | Our team of full-time analysts conducts daily monitoring of various platforms, including hacker forums on the surface web, darknet, and Telegram channels. Each analyst is assigned a clearly defined area of focus, ensuring comprehensive coverage across different sources. | ||
+ | |||
+ | When we discover a data breach being offered for free, we promptly download and thoroughly investigate it. For breaches listed for sale, we acquire sample data whenever possible to notify our clients if their sensitive information might be at risk of exposure. | ||
+ | |||
+ | All collected information that could hold value for our clients is meticulously indexed. This includes a variety of formats, such as database files (e.g., SQL dumps), physical documents (e.g., Word, Excel, PDF), or text-based leak data (e.g., CSV or TXT files). Each breach undergoes a strict internal verification process by our team to confirm its authenticity and relevance. | ||
+ | |||
+ | Once verified, we enrich the data with metadata to provide essential context. Metadata includes details such as the source of the leak, the date of the breach, the type of data involved, and other relevant information. After this process, the verified and indexed data is uploaded to our system, making it searchable and accessible to all clients for further investigation. | ||
+ | |||
+ | **Key Explanations for Potentially Unclear Terms:** | ||
+ | * Surface web: The publicly accessible portion of the internet that standard search engines like Google can index. | ||
+ | * Darknet: A part of the internet that requires specific software (e.g., Tor) to access. It's often associated with anonymity and illegal activities but is also used for privacy purposes. | ||
+ | * Telegram channels: Groups or channels on the Telegram messaging platform, commonly used for communication and sharing information, | ||
+ | * SQL dumps: Copies of entire databases, often leaked during breaches. | ||
+ | * CSV/TXT files: Common formats for storing text data, typically containing structured information like lists, logs, or tables. | ||
+ | * Metadata: Additional information about a file or data set that helps to describe, organize, and manage the data more effectively (e.g., time, location, type). | ||
+ | |||
+ | ==== How up to date and accurate | ||
+ | |||
+ | Our credential database is updated daily by a dedicated team of analysts who actively monitor and extract data from hacker forums, Telegram channels, and various darknet sources. The credentials available in our database search are those that have already been publicly leaked—often because hackers failed to sell them and instead chose to distribute them for free. | ||
+ | |||
+ | If you are searching for newer, actively traded credentials, | ||
+ | |||
+ | **Data Accuracy and Duplicate Entries** | ||
+ | |||
+ | Credential leaks often get repackaged and redistributed in collections and archives, leading to duplicate entries. While our system works to filter out redundancies, | ||
+ | |||
+ | Furthermore, | ||
+ | |||
+ | * Users change their passwords after a breach is exposed. | ||
+ | * Accounts may be deleted or suspended by the service provider. | ||
+ | * Credentials become obsolete as new security measures are implemented. | ||
+ | |||
+ | The older the dataset, the higher the probability that the credentials are no longer functional. Since these credentials are publicly available, they are accessible to anyone, diminishing their immediate value to attackers. | ||
+ | |||
+ | **Why Monitoring is More Important than Retrospective Analysis** | ||
+ | |||
+ | Rather than relying solely on static historical reports, continuous monitoring of leaked credentials is essential. A one-time report over an extended period is not as effective as ongoing surveillance because: | ||
+ | Even if 99% of leaked credentials are outdated, the remaining 1% of active credentials still pose a security risk. | ||
+ | |||
+ | Leaked credentials provide critical intelligence beyond just direct access, such as: | ||
+ | |||
+ | * Employee usage of third-party services with company accounts (e.g., logging into Netflix or other non-business platforms using corporate credentials). | ||
+ | * Password patterns that reveal predictable behavior. For example, if a user previously used Summer2024, there' | ||
+ | * Cross-service password reuse, which allows attackers to map out vulnerabilities across multiple platforms. | ||
+ | * Exposure assessment, measuring how frequently an employee' | ||
- | The database is updated daily from our analysts. We use different [[how_do_we_find_the_data_in_kaduu|discovery methods]] (manual and automated). | ||
===== What is a leak? ===== | ===== What is a leak? ===== |