Abstract: Techniques for identity management for permissions are described. According to various embodiments, a user establishes a communication relationship with another user, referred to herein as a “contact.” According to various embodiments, the contact is associated with multiple identities. Accordingly, embodiments discussed herein enable a primary identity to be specified such that permissions for the primary identity are enforced for interactions with the contact. Further, techniques discussed herein enable a primary identity to be updated based on a change in identity state of a contact.

Abstract: Techniques for identity management for permissions are described. According to various embodiments, a user establishes a communication relationship with another user, referred to herein as a “contact.” According to various embodiments, the contact is associated with multiple identities. Accordingly, embodiments discussed herein enable a primary identity to be specified such that permissions for the primary identity are enforced for interactions with the contact. Further, techniques discussed herein enable a primary identity to be updated based on a change in identity state of a contact.

Abstract: Systems and methods to deliver malformed data for software application fuzzing are described. In one aspect, a fuzzing engine receives well-formed valid input data from a test automation tool. The received data is for input into a software application to implement a functional test. Responsive to receiving the well-formed valid input data, the fuzzing engine automatically generates corresponding malformed data based on characteristics of the well-formed valid input data. The application is then automatically fuzzed with the malformed data to notify an end-user of any security vulnerabilities in one or more code paths of the application used to process the malformed data.

Abstract: A test tool is provided for testing a software component. The tool receives data structured and formatted for processing by the software component. The structured data might conform to a schema defining valid inputs that the software component is able to parse/process. The test tool selects a discrete part of the structured data and fuzzes the selected discrete part. The test tool determines whether there are any parts of the structured data whose validity can be affected by fuzzing of the discrete part of the structured data. The fuzzed discrete part of the structured data is analyzed and a related part of the structured data is updated to be consistent with the fuzzed discrete part. The fuzzing tool passes the structured data with the fuzzed part and the updated part to the software component being tested. The software component is tested by having it process the data.

Abstract: A test tool is provided for testing a software component. The tool receives data structured and formatted for processing by the software component. The structured data might conform to a schema defining valid inputs that the software component is able to parse/process. The test tool selects a discrete part of the structured data and fuzzes the selected discrete part. The test tool determines whether there are any parts of the structured data whose validity can be affected by fuzzing of the discrete part of the structured data. The fuzzed discrete part of the structured data is analyzed and a related part of the structured data is updated to be consistent with the fuzzed discrete part. The fuzzing tool passes the structured data with the fuzzed part and the updated part to the software component being tested. The software component is tested by having it process the data.

Abstract: Systems and methods to test software applications with schema-based fuzzing are described. In one aspect, the systems and methods automatically generate valid input data for a software application according to a fuzzing data schema. The fuzzing data schema describes characteristics of data format that would be proper or well formed for input into the software application. The systems and methods mutate to the valid input data with one or more fuzzing algorithms to generate corrupted versions, or malformed data. The malformed data is for fuzz testing the software application to identify any security vulnerabilities.

Abstract: A test tool is provided for testing a software component. The tool receives data structured and formatted for processing by the software component. The structured data might conform to a schema defining valid inputs that the software component is able to parse/process. The test tool selects a discrete part of the structured data and fuzzes the selected discrete part. The test tool determines whether there are any parts of the structured data whose validity can be affected by fuzzing of the discrete part of the structured data. The fuzzed discrete part of the structured data is analyzed and a related part of the structured data is updated to be consistent with the fuzzed discrete part. The fuzzing tool passes the structured data with the fuzzed part and the updated part to the software component being tested. The software component is tested by having it process the data.

Abstract: A test tool is provided for testing a software component. The tool receives data structured and formatted for processing by the software component. The structured data might conform to a schema defining valid inputs that the software component is able to parse/process. The test tool selects a discrete part of the structured data and fuzzes the selected discrete part. The test tool determines whether there are any parts of the structured data whose validity can be affected by fuzzing of the discrete part of the structured data. The fuzzed discrete part of the structured data is analyzed and a related part of the structured data is updated to be consistent with the fuzzed discrete part. The fuzzing tool passes the structured data with the fuzzed part and the updated part to the software component being tested. The software component is tested by having it process the data.

Abstract: Systems and methods to test software applications with schema-based fuzzing are described. In one aspect, the systems and methods automatically generate valid input data for a software application according to a fuzzing data schema. The fuzzing data schema describes characteristics of data format that would be proper or well formed for input into the software application. The systems and methods mutate to the valid input data with one or more fuzzing algorithms to generate corrupted versions, or malformed data. The malformed data is for fuzz testing the software application to identify any security vulnerabilities.

Abstract: Systems and methods to deliver malformed data for software application fuzzing are described. In one aspect, a fuzzing engine receives well-formed valid input data from a test automation tool. The received data is for input into a software application to implement a functional test. Responsive to receiving the well-formed valid input data, the fuzzing engine automatically generates corresponding malformed data based on characteristics of the well-formed valid input data. The application is then automatically fuzzed with the malformed data to notify an end-user of any security vulnerabilities in one or more code paths of the application used to process the malformed data.