In the provided exhibit of theCisco Data Loss Prevention (DLP) Policyinterface (likely within Cisco Umbrella or a similar cloud security gateway), the reason for the policy's failure to stop the upload is clearly visible in the "Action" column. The rule named"ChatGPT Source Code"is currently configured with the action set toMonitor.
According to theCisco SDSI v1.0objectives regarding application and data security, theMonitoraction is designed for visibility and auditing. It allows the traffic to pass through while generating a log entry for security analysts to review. This is often used during an initial "discovery" phase to understand how data is moving without disrupting business processes. However, to fulfill the requirement ofpreventingthe unauthorized upload of sensitive data-such as application source code-the policy must be enforcement- centric.
By selectingOption D, the developer changes the action from "Monitor" toBlock. In "Block" mode, the DLP engine will actively intercept the web request to ChatGPT, inspect the content for "Source Code" classifications, and drop the connection if a match is found, thereby preventing the data from leaving the corporate environment. While moving rules (Option B) can resolve conflicts if a "Block" rule is superseded by an "Allow" rule higher in the list, the primary issue here is the non-restrictive action of the specific rule itself. Modifying data classifications (Option C) is unnecessary if the engine is already correctly identifying the source code, as evidenced by the successful monitoring logs mentioned in the scenario. Changing the action to Block is the definitive step to ensure data integrity and prevent intellectual property theft.