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\u003eThe webpage provides reference documentation for the \u003ccode\u003eExfilResource\u003c/code\u003e class within the Google Cloud Security Center v1 API, detailing its structure and usage.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eExfilResource\u003c/code\u003e is a class that represents a resource from which data was exfiltrated or to which it was exfiltrated.\u003c/p\u003e\n"],["\u003cp\u003eThe class implements interfaces like \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e, and inherits from \u003ccode\u003eobject\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation includes information on the \u003ccode\u003eExfilResource\u003c/code\u003e class constructors and properties such as \u003ccode\u003eComponents\u003c/code\u003e (a list of subcomponents) and \u003ccode\u003eName\u003c/code\u003e (the resource's full name).\u003c/p\u003e\n"],["\u003cp\u003eMultiple versions of the \u003ccode\u003eExfilResource\u003c/code\u003e class are documented, ranging from version 2.2.0 to the latest version 3.24.0, with links to the API documentation for each.\u003c/p\u003e\n"]]],[],null,[]]
