Abstract: Techniques are described herein that are capable of performing a security action based on cross-tenant security threat analysis using a multi-tenant identifier. First and second security data are gathered from first and second resources in first and second security-bounded tenants and stored in a tenant-shared store using first and second tenant-specific identifiers. A cross-tenant security threat analysis is performed with regard to the first and second security-bounded tenants by using a multi-tenant identifier to obtain multi-tenant permission to access the first security data and the second security data in the tenant-shared store. As a result of the cross-tenant security threat analysis indicating a security threat with regard to the first security-bounded tenant and/or the second security-bounded tenant, execution of an instruction is triggered, which causes a security action to be performed with regard to the first security-bounded tenant and/or the second security-bounded tenant.

Abstract: Techniques are described herein that are capable of performing metadata extraction based on resource attributes and user-defined policy and topology. A hierarchical resource-grouping construct, which is selected from hierarchical resource-grouping constructs in a user-defined hierarchical resource-grouping topology of a cloud computing service account, is registered by enumerating at least a subset of the constructs. The subset includes the selected construct and each other construct encompassed by the selected construct. Metadata is selectively extracted from the constructs that are included in the subset to provide extracted metadata based at least in part on one or more user-defined policies, which are assigned among the constructs that are included in the subset, indicating whether the metadata is to be extracted as a result of resources associated with the constructs included in the subset having specified attributes. A searchable catalog is generated that includes the extracted metadata.

Abstract: Techniques are described herein that are capable of performing metadata extraction based on resource attributes and user-defined policy and topology. A hierarchical resource-grouping construct, which is selected from hierarchical resource-grouping constructs in a user-defined hierarchical resource-grouping topology of a cloud computing service account, is registered by enumerating at least a subset of the constructs. The subset includes the selected construct and each other construct encompassed by the selected construct. Metadata is selectively extracted from the constructs that are included in the subset to provide extracted metadata based at least in part on one or more user-defined policies, which are assigned among the constructs that are included in the subset, indicating whether the metadata is to be extracted as a result of resources associated with the constructs included in the subset having specified attributes. A searchable catalog is generated that includes the extracted metadata.

Abstract: Techniques are described herein that are capable of performing metadata extraction based on resource attributes and user-defined policy and topology. A hierarchical resource-grouping construct, which is selected from hierarchical resource-grouping constructs in a user-defined hierarchical resource-grouping topology of a cloud computing service account, is registered by enumerating at least a subset of the constructs. The subset includes the selected construct and each other construct encompassed by the selected construct. Metadata is selectively extracted from the constructs that are included in the subset to provide extracted metadata based at least in part on one or more user-defined policies, which are assigned among the constructs that are included in the subset, indicating whether the metadata is to be extracted as a result of resources associated with the constructs included in the subset having specified attributes. A searchable catalog is generated that includes the extracted metadata.

Abstract: Techniques are described herein that are capable of performing metadata extraction based on resource attributes and user-defined policy and topology. A hierarchical resource-grouping construct, which is selected from hierarchical resource-grouping constructs in a user-defined hierarchical resource-grouping topology of a cloud computing service account, is registered by enumerating at least a subset of the constructs. The subset includes the selected construct and each other construct encompassed by the selected construct. Metadata is selectively extracted from the constructs that are included in the subset to provide extracted metadata based at least in part on one or more user-defined policies, which are assigned among the constructs that are included in the subset, indicating whether the metadata is to be extracted as a result of resources associated with the constructs included in the subset having specified attributes. A searchable catalog is generated that includes the extracted metadata.

Abstract: In some examples, a computing device determines a data manipulation from a job specification. The device determines a corresponding data-processing instruction using data-source metadata, and determines and executes a corresponding query. In some examples, a device receives search keys. The device searches data-source metadata using the search keys. The device weights a first data source based on producer-consumer relationships between data sources, and ranks the first data source using the weight. In some examples, a device determines structural and content information of a data record. The device determines a data-source identifier from the structural information and stores the content information with the data-source identifier in a database. In some examples, via a user interface, a device receives a job specification and annotation data. The device stores the spec and the annotation data in a metadata repository.

Abstract: Data assets, such as streams, databases, spreadsheets, or other data sources or types, are identified and representations of the data asset are stored. The representation of a data asset includes a schema used by the data asset, a location of the data asset, and keywords or other descriptive information. The representations of each data asset are indexed, and a search interface is provided that allows users to search for relevant data assets. In addition, dependencies, or other relationship information, among the various data assets is maintained and is used to generate a graph that shows the interrelatedness of the data assets. The graph can be explored by users to select data assets, and used to alert users when a change has been made to a data asset that may affect a data asset that they have used.

Abstract: Data assets, such as streams, databases, spreadsheets, or other data sources or types, are identified and representations of the data asset are stored. The representation of a data asset includes a schema used by the data asset, a location of the data asset, and keywords or other descriptive information. The representations of each data asset are indexed, and a search interface is provided that allows users to search for relevant data assets. In addition, dependencies, or other relationship information, among the various data assets is maintained and is used to generate a graph that shows the interrelatedness of the data assets. The graph can be explored by users to select data assets, and used to alert users when a change has been made to a data asset that may affect a data asset that they have used.

Abstract: In some examples, a computing device determines a data manipulation from a job specification. The device determines a corresponding data-processing instruction using data-source metadata, and determines and executes a corresponding query. In some examples, a device receives search keys. The device searches data-source metadata using the search keys. The device weights a first data source based on producer-consumer relationships between data sources, and ranks the first data source using the weight. In some examples, a device determines structural and content information of a data record. The device determines a data-source identifier from the structural information and stores the content information with the data-source identifier in a database. In some examples, via a user interface, a device receives a job specification and annotation data. The device stores the spec and the annotation data in a metadata repository.

Abstract: A method includes displaying a plurality of user modifiable utilization views of a monitored software application, where each of the plurality of user modifiable utilization views is customizable to fit a domain of analysis by identifying one or more resource types of multiple resource components. Each of the plurality of user modifiable utilization views is displayed in one more graphical user interfaces. The method includes determining a desired ordering of the one or more resource types within a hierarchy of types and filtering one or more details of the multiple resource components to create a customized view. A user can navigate between each of the plurality of user modifiable utilization views to dynamically construct related target analysis views including filtered details across one or more other domains of analysis.