Configure Identifiers

identifier types an identifier is a defined data point used to detect and track relevant external threats across monitored sources to support diverse monitoring needs, flare offers a flexible set of identifier types, including domain, identity, keyword, bin, ip address, and custom identifiers each type serves a specific investigative purpose, helping you build a precise and proactive defense posture domain domain identifiers are used to search for activities related to a domain name when the system searches for a domain name on the criminal underground or the clear web, it looks for a precise match aligned with the following rules with a domain like foo com foo com , bar foo com , or foo com au is a match foo2 com , or foo comment is not a match with a subdomain like foo bar com foo bar com , abc foo bar com , foo bar com au is a match foo bar comment , foofoo bar com , foo bar au com , bar com , or com is not a match note identifiers are not case sensitive this is true for across all source types we will identify whether domains are reachable or resolvable with these icons in flare, reachable is a subset of resolvable a resolvable domain means the dns successfully translates it to an ip address a reachable domain means our system can establish a connection with that ip a domain may be resolvable but not reachable for several reasons, including the ip is no longer in service the ip requires authentication (e g , private/internal ips) the connection attempt times out there may be other causes, but these are the most common if you encounter a domain that is resolvable but not reachable, we recommend further investigation if you believe a domain should be reachable but isn’t, please report it as a potential bug so our team can troubleshoot you are also able to filter domains by their dns record and host status , and apply these filters by date subdomain identifiers are important for certain cases auto enumerating subdomain identifiers provides more comprehensive visibility across your attack surface look alike domain detection; individual subdomain identifiers are required for stealer logs; when a subdomain is the authorization url or in the email, we wouldn't match it without the specific subdomain identifier for leaked credentials; any email addresses associated with subdomains wouldn't be found without the specific subdomain identifier for the majority of our dark web sources; chatter involving a subdomain will be missed without the specific subdomains identifiers domain authorization domain authorization is required to access certain categories of information, including domain specific credentials and personally identifiable information (pii) linked to events within a domain organizations can request authorization for their primary domain by submitting an authorization request once granted, the standard domain identifier can reveal pii linked to events within that domain click through the following demo to learn how to submit a domain authorization request bulk authorization to request authorization for multiple domain identifiers, select the identifiers and then click the request authorization option from the context menu bulk authorization supports up to 10 domain identifiers at a time to authorize more than 10, please submit the requests in separate batches if domain identifiers are organized into a group, selecting the group does not authorize the identifiers within it select the individual domain identifiers inside the group, then request authorization from the context menu identity identifiers identity identifiers are used to search for people related activities, specifically with their first and last names you can add email, name (first name/last name) and username as attributes in the same identity identifier name attributes have an optional setting called strict mode when enabled, flare will only search for activities that contain subsequent first name and last name this can help reduce false positives for people with common first names for example, you are likely to find leaked passwords results or discussions of a person or business alongside their email address, name or username on the open web we will show the leaked passwords associated with the specific attributes, search for mention of this email on clear web and dark web, and track any commits made to source code repository websites there are two ways to create an identity identifier manually create an identity identifier (unauthorized) sync your identities from entra id (authorized) keyword keyword identifiers are used to search for activities related to specific keywords for example, you can search for your organization's name or brand names and monitor for mentions of those keywords on the dark web flare also uses keyword identifiers to do data collection keyword identifiers will be used to search on different platforms flare monitors (like github, twitter, shodan, etc ) any results that are found will then be added to flare so that you can view them in your event feeds https //docs flare systems/browse an event feed azure tenant azure tenant identifiers are used to search for events containing mentions of an azure tenant this type of identifier functions similarly to the keyword type the main difference between the two is that identifier recommendations will recommend azure tenant type identifiers when a monitored domain is found to be linked to a microsoft azure tenant monitoring for an azure tenant id is a great way to detect secrets on github (or other sources) when there is no reference to the domain of your organization due to configuration files containing azure tenant id's bin bin identifiers are used to search for activities related to credit card numbers, starting with the specified bank identification numbers enter the first numbers of the card without spaces flare handles any spaces that might appear in the crawled content and keeps only the card numbers that match the luhn algorithm for example, with bin 52588 5258 8199 1008 5316 match 5258819910085316 match 5 2 5 8 8 1 9 9 1 0 0 8 5 3 1 6 match 52 588 1991 0085316 match a regex can also be used for example, with bin 52588\[0 1] 5258 8199 1008 5316 match 5258 8299 1008 5315 no match ip address ip address identifiers are used to search for activities related to ip addresses this is particularly useful for monitoring open ports or to look for technical information leaks related to addresses in your public ip range both specific ip addresses and cidr ip ranges are supported for example 172 1 1 35, 172 1 1 0/24 query query identifiers are used to filter events by field or through regex patterns to search for terms that do not fit any other identifier type search queries are written using lucene query syntax https //lucene apache org/core/2 9 4/queryparsersyntax html to find events indexed before the identifier was created, the query or regex can be pasted into flare's search bar to search historical data see search in existing data docid 8ykwptlf5d76xqwa1fwyv for syntax details and examples important to note queries used in a query identifier can have 1000 words separated by boolean operators and a nested structure of 20 levels deep maximum query identifiers do not match events in real time they check for new events once every 24 hours, so a new matched event may take up to a day to appear in your feed if real time detection is needed, use matching policies for identifiers docid\ zg1zxobulcijhudrj hkg with other identifier types, since those generate matched events as soon as new events come in github repository github repository identifiers allow you to specify both a repository owner and repository name on github and then monitor for new activities that match the information provided password password identifiers allow you to monitor the clear and dark web for mentions of a password you know this can be helpful for locating mentions of a previously leaked password to better understand how potential threat actors might discuss it on the web threat categories a threat category is a predefined set of the individual categories most relevant to a particular type of threat selecting a threat category pre selects its recommended categories as a starting point, which you can then customize these selections are recommendations rather than restrictions you can select any combination of individual categoriess and remove any that are not required before saving you can also select multiple threat categories, search for an individual category/data source, or click unselect all to clear the current selection the complete set of threat categories and the individual categories each one pre selects is shown below not all threat categories appear for every identifier type threat category individual categories identity exposure infected devices, leaked credentials, pastes, chats dark web monitoring pastes, chats, market, ransom leaks, blog posts, financial data, profiles domain impersonation lookalike domain technical exposure buckets, source code by default, some individual categories are unavailable for certain identifier types to avoid returning zero results or false positives the categories available per identifier type are as follows identifier type available categories domain all illicit networks, pastes, source code, google, hosts, buckets, leaked credentials, lookalike domains keyword all illicit networks, pastes, source code, google, hosts, buckets identity all illicit networks, pastes, source code, google, leaked credentials azure tenant all illicit networks, source code, google, hosts, buckets query all illicit networks, pastes bin all illicit networks, pastes, google ip address all illicit networks, pastes, source code, google, hosts password leaked credentials github repository source code for all identifier types, emerging sources are disabled by default but can be manually enabled if needed severity select the minimal alert severity to ignore less critical events associated with this identifier to learn more about severities, see understand severity scoring https //docs flare io/understand scoring matching policies matching policies are a per identifier filtering system that gives you precise control over which events appear in an identifier's feed with matching policies, you can include or exclude events based on keywords, or refine results using a full lucene search query more details are available on the matching policies for identifiers docid\ zg1zxobulcijhudrj hkg page add to group you can add this identifier to an existing identifiers group to create a group, go to the ‘identifiers’ tab > click on ‘create group’ > give it a name, add it to an existing group if necessary > click on “create group” when you’re done alerts you now have the ability to create alerts directly from a specific identifier within the identifiers section all configured alerts can be viewed in alert central https //docs flare io/alert central , where the targeted identifier is displayed in the identifier scope column related articles