Subcomponents of the asset that was exfiltrated, like URIs used during
exfiltration, table names, databases, and filenames. For example, multiple
tables might have been exfiltrated from the same Cloud SQL instance, or
multiple files might have been exfiltrated from the same Cloud Storage
bucket.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThis webpage provides reference documentation for the \u003ccode\u003eExfilResource\u003c/code\u003e class within the Google Cloud Security Command Center v1 API, spanning multiple versions.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eExfilResource\u003c/code\u003e represents a resource where data was either taken from or sent to and is used to identify the data during exfiltration in Security Command Center.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation covers versions from 2.2.0 up to the latest 3.24.0, including version 3.23.0 which is what the main documentation is based around.\u003c/p\u003e\n"],["\u003cp\u003eThe class implements multiple interfaces, including \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e, and also shows the inheritance from \u003ccode\u003eobject\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eExfilResource\u003c/code\u003e has properties such as \u003ccode\u003eComponents\u003c/code\u003e, for listing the subcomponents involved in exfiltration, and \u003ccode\u003eName\u003c/code\u003e, for specifying the full resource name.\u003c/p\u003e\n"]]],[],null,[]]
