# US 2021/0334395 A1 · System and Method for Implementing and testing Security Protections in Computer Software

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0334395 A1
- Document ID: US20210334395A1
- Status: Published application
- Kind: A1
- Application number: 16/479,786
- Filed: 2018-01-22
- Published: 2021-10-28
- Earliest claimed: 2017-01-23
- Assignees: Uleska Ltd.
- Applicants: Uleska Ltd.
- Inventors: Gary Robinson
- Web page: https://patentgrep.com/patent/US20210334395A1

## CPC

- G06F 21/629: {to features or functions of an application}
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F 11/3692: {for test results analysis}
- G06F 21/45: Structures or tools for the administration of authentication
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- G06F 11/3672: {Test management}
- G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A computer implemented method of applying a technical application security posture to a software project is described. The method allows an industry or corporate wide technical security posture to be enumerated. It further allows multiple software applications to be represented based on existing or proposed software (source code) producing a model representation of the application. Implementations of the technical security posture can then be combined with the software application model to ensure the necessary technical security posture is applied to the application implementation.

## Claims

### Claim at position 1

1-34. (canceled)

### Claim 35

A method of implementing a security posture comprising at least one security requirement for a computer software application, the method comprising:
providing, on a computer system, a security protection component comprising at least one set of at least one computer-usable instruction;
providing, on said computer system, a computer-usable representation of said security posture;
providing, on said computer system, a computer-usable model of said computer software application; and
causing said computer system to use said at least one computer-usable instruction and said computer-usable representation of said security posture and said computer-usable model of said computer software application to generate at least one computer usable output for implementing said at least one security requirement.

### Claim 36 (depends on 35)

The method of claim 35, wherein said causing said computer system to use said at least one set of at least one computer-usable instruction involves populating, or otherwise configuring, at least one of said at least one instruction with data from said security posture, and/or selecting at least one of said at least one instruction depending on said security posture.

### Claim 37 (depends on 35)

The method of claim 35, including causing said computer system to provide a user interface, said user interface being defined by at least one of said at least one set of at least one computer-usable instruction; and creating, in response to user input received by said user interface, said computer-usable representation of said security posture, wherein, preferably, said at least one of said at least one set of at least one computer-usable instruction comprises a respective interface template for each of said security requirements, wherein each interface template is configured to provide said user interface with at least one user input element for at least one of said security requirements.

### Claim 38 (depends on 35)

The method of claim 35, wherein said at least one set of at least one computer-usable instruction comprises at least one requirement instruction comprising one or more computer-renderable instructions for implementing at least one of said security requirements, wherein the method typically includes populating, or otherwise configuring, at least one of said at least one requirement instruction with data from said security posture, and/or selecting at least one of said at least one requirement instruction depending on said security posture.

### Claim 39 (depends on 35)

The method of claim 35, wherein said at least one set of at least one computer-usable instruction comprises at least one code instruction comprising computer-usable instructions for implementing at least one of said security requirements, wherein the method typically includes populating, or otherwise configuring, at least one of said at least one code instruction with data from said security posture, and/or selecting at least one of said at least one code instruction depending on said security posture.

### Claim 40 (depends on 35)

The method of claim 35, wherein said at least one set of at least one computer-usable instruction comprises at least one assurance instruction comprising computer-usable instructions for testing at least one of said security requirements, the method typically including populating, or otherwise configuring, at least one of said at least one assurance instruction with data from said security posture, and/or selecting at least one of said at least one assurance code instruction depending on said security posture.

### Claim 41 (depends on 35)

The method of claim 35, wherein said model comprises data defining at least one interface supported by said software application.

### Claim 42 (depends on 35)

The method of claim 35, wherein generating said at least one computer usable output involves combining at least one of said at least one set of at least one computer-usable instruction and said computer-usable representation of said security posture and said computer-usable model of said computer software application.

### Claim 43 (depends on 35)

The method of claim 35, wherein generating said at least one computer-usable output involves populating, or otherwise configuring, at least one of said at least one set of at least one instruction with data from said security posture, and/or selecting at least one of said at least one set of at least one instruction depending on said security posture.

### Claim 44 (depends on 35)

The method of claim 35, wherein generating said at least one computer-usable output involves identifying from said computer-usable model at least one feature of said software application relating to at least one of said at least one security requirements, and selecting and/or populating, or otherwise configuring, at least one of said at least one set of at least one instruction using said security posture depending on said at least one identified feature of said software application.

### Claim 45 (depends on 38)

The method of claim 38, wherein generating said at least one computer-usable output involves populating, or otherwise configuring, at least one of said at least one requirement instruction with data from said security posture and/or selecting at least one of said at least one requirement instruction depending on said security posture.

### Claim 46 (depends on 38)

The method of claim 38, wherein said at least one computer-usable output comprises one or more computer-renderable instructions for implementing at least one of said security requirements.

### Claim 47 (depends on 38)

The method of claim 38, wherein generating said at least one computer-usable output involves identifying from said computer-usable model at least one feature of said software application relating to at least one of said at least one security requirements, and selecting and/or populating, or otherwise configuring, at least one of said at least one requirement instruction using said security posture depending on said at least one identified feature of said software application.

### Claim 48 (depends on 39)

The method of claim 39, wherein generating said at least one computer-usable output involves populating, or otherwise configuring, at least one of said at least one code instruction with data from said security posture and/or selecting at least one of said at least one code instruction depending on said security posture.

### Claim 49 (depends on 39)

The method of claim 39, wherein said at least one computer-usable output comprises one or more computer-usable instructions for implementing at least one of said security requirements.

### Claim 50 (depends on 39)

The method of claim 39, wherein generating said at least one computer-usable output involves identifying from said computer-usable model at least one feature of said software application relating to at least one of said at least one security requirements, and selecting and/or populating, or otherwise configuring, at least one of said at least one code instruction using said security posture depending on said at least one identified feature of said software application.

### Claim 51 (depends on 40)

The method of claim 40, wherein generating said at least one computer-usable output involves populating, or otherwise configuring, at least one of said at least one assurance instruction with data from said security posture and/or selecting at least one of said at least one assurance templates depending on said security posture.

### Claim 52 (depends on 40)

The method of claim 40, wherein said at least one computer-usable output comprises one or more computer-usable instructions for testing at least one of said security requirements.

### Claim 53 (depends on 40)

The method of claim 40, wherein generating said at least one computer-usable output involves identifying from said computer-usable model at least one feature of said software application relating to at least one of said at least one security requirements, and selecting and/or populating, or otherwise configuring, at least one of said at least one assurance instruction using said security posture depending on said at least one identified feature of said software application.

### Claim 54 (depends on 35)

The method of claim 35, wherein generating said at least one computer-usable output involves identifying from said computer-usable model at least one feature of said software application relating to at least one of said at least one security requirements and, depending on said at least one identified feature of said software application: populating, or otherwise configuring, at least one of said at least one code instruction with data from said security posture; and/or selecting at least one of said at least one code instruction depending on said security posture.
