|
6 | 6 |
|
7 | 7 | ---
|
8 | 8 |
|
| 9 | +import { Details } from "~/components" |
| 10 | + |
9 | 11 | :::note
|
10 | 12 | You must have a Cloudforce One subscription to access Cloudforce One on the dashboard.
|
11 | 13 | :::
|
@@ -35,6 +37,36 @@ To submit RFIs (Request for Information):
|
35 | 37 | 3. Select **New Request**.
|
36 | 38 | 4. Fill in the required fields, then select **Save**.
|
37 | 39 |
|
| 40 | +<Details header="List of RFI types"> |
| 41 | + |
| 42 | +The Cloudflare dashboard presents the following request types when you want to configure a Cloudforce One Requests for Information: |
| 43 | + |
| 44 | +- **Binary Analysis - IOCs**: Conduct high level malware analysis to produce [indicators](https://www.cloudflare.com/en-gb/learning/security/what-are-indicators-of-compromise/) such as a call-back domain or IP address. |
| 45 | + |
| 46 | +- **Binary Analysis - Report**: A thorough analysis of a malware sample to produce an attribution assessment and extract the configuration of the sample for further analysis. Useful for customers that are investigating a problem or trying to develop detection logic in an [EDR](https://en.wikipedia.org/wiki/Endpoint_detection_and_response) or network sensor. |
| 47 | + |
| 48 | +- **DDoS Attack**: Confirm if an attack is happening against a specific website to share any available indicators and potential attribution. |
| 49 | + |
| 50 | +- **Indicator Analysis - IOCs**: Conduct DNS lookups, origin pivots, and account pivots to provide indicators such as DNS resolutions, origin IPs, and subdomains. Analysis can include account registration patterns and victimology. |
| 51 | + |
| 52 | +- **Indicator Analysis - Report**: A thorough analysis of indicators written in a formal, structured format. In addition to listing [Indicator of compromise (IOCs)](https://www.cloudflare.com/en-gb/learning/security/what-are-indicators-of-compromise/), the report explains how IOCs function within the attack chain, and adds context by linking IOCs to specific campaigns and/or threat actors and their TTPs. |
| 53 | + |
| 54 | +- **Passive DNS Resolution**: Research the pair of an IP address to the domain it resolved to during a specified period of time. |
| 55 | + |
| 56 | +- **Strategic Threat Research**: Strategic Threat Research goes beyond simple indicators to analyze broader, long-term trends, threat actors, and industries — often supplemented by open-source intelligence to inform high-level management and planning rather than providing immediately actionable intelligence. |
| 57 | + |
| 58 | +- **Threat Detection Signature - IOCs**: Develop a rule such as Yara that will detect a sample, behavior, or network observable such as an IP address, domain, file hash, or attribute of a file or HTTP request. |
| 59 | + |
| 60 | +- **Threat Detection Signature - Report**: A thorough analysis report that investigates the details of a threat detection alert or report for the benefit of customers that are trying to prioritize their response effort or to attribute activity to a threat actor. |
| 61 | + |
| 62 | +- **Traffic Analysis - IOCs**: Review HTTP telemetry of IOCs in question and provide relevant, sanitized traffic which can include victim country and in some cases victim ASNs. Identify malicious files/payloads, and unusual file paths or request patterns. |
| 63 | + |
| 64 | +- **Traffic Analysis - Report**: Report that analyzes HTTP telemetry to identify patterns, anomalies, and data pointing to malicious behavior. Provides context for observed network behaviors and maps them to known TTPs of specific threat groups. |
| 65 | + |
| 66 | +- **Vulnerability**: Investigation to attribute vulnerability exploitation to a threat actor or investigation of IPs, domains, or threat actor groups exploiting the vulnerability. Response can include relevant, sanitized traffic demonstrating exploitation and identification of victim countries and industries. |
| 67 | + |
| 68 | +</Details> |
| 69 | + |
38 | 70 | Once you select **Save**, the dashboard will display an overview of the shared information consisting of:
|
39 | 71 |
|
40 | 72 | - **Status**: When you submit the RFI, the status is `Open`. Once the team accepts the RFI, the status changes to `Accept`. When the team commits to answer your RFI, the status changes to `Complete`.
|
|
0 commit comments