# US 11,442,755 B1 · Secure access to a corporate application using a facade

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

- Number: US 11,442,755 B1
- Document ID: US11442755B1
- Status: Granted
- Kind: B1
- Application number: 16/591,335
- Filed: 2019-10-02
- Granted: 2022-09-13
- Earliest claimed: 2019-04-10
- Assignees: CA, Inc.
- Applicants: CA, Inc.
- Inventors: David Patimer; Lior Lev-Tov; Eldad Rudich; Leonid Belkind
- Web page: https://patentgrep.com/patent/US11442755B1

## CPC

- H04L 63/102: {Entity profiles}
- G06F 9/452: {Remote windowing, e.g. X-Window System, desktop virtualisation (protocols for virtual reality H04L67/131)}
- G06F 21/305: {by remotely controlling device operation}
- G06F 21/33: using certificates
- H04L 63/02: {for separating internal from external traffic, e.g. firewalls}
- H04L 63/0281: {Proxies}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L 67/147: Signalling methods or messages providing extensions to protocols defined by standardisation
- H04L 67/562: Brokering proxy services
- H04L 69/22: Parsing or analysis of headers
- H04L 61/2514: between local and global IP addresses
- H04L 63/0272: {Virtual private networks}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/205: {involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved (negotiation of communication capabilities H04L69/24)}
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Secure access to a corporate application using a facade. In some embodiments, a method may include receiving, at a secure access cloud point of delivery (PoD), from a client application on a client device, a request to access a corporate application that is deployed in a corporate datacenter. The method may also include creating, at the secure access cloud PoD, a facade representing the corporate application. The method may further include forwarding, from the facade, to a connector that is also deployed in the corporate datacenter, the request. The method may also include brokering, by the connector and the facade, authentication of a user, authorization of access by the user, and a secure communication session between the client application and the corporate application via the facade, with the client application being unaware that the secure communication session is brokered by the connector and the facade.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving, at a secure access cloud point of delivery (PoD), from a client application on a client device, a request to access a corporate application that is deployed in a corporate datacenter, wherein the secure access cloud PoD is isolated from the corporate datacenter;
creating, at the secure access cloud PoD, a facade representing the corporate application, wherein the façade replicates, at least in part, portions of the corporate application;
forwarding, from the facade at the secure access cloud PoD, to a connector that is also deployed in the corporate datacenter, the request to access the corporate application; and
brokering, by the connector and the facade at the secure access cloud PoD, authentication of a user, authorization of access by the user, and a secure communication session between the client application and the corporate application via the facade, with no corresponding agent being installed at the client device, and with the client application being unaware that the secure communication session is brokered by the connector and the facade at the secure access cloud PoD, wherein brokering the secure communication session between the client application and the corporate application includes establishing a communication channel between the facade at the secure access cloud PoD and the connector, and wherein communication between the client application and the corporate application is conducted via the facade at the secure access cloud PoD and the connector at the corporate datacenter over the communication channel.

### Claim 2 (depends on 1)

The method of claim 1, wherein the facade poses as the corporate application and behaves similarly to the corporate application.

### Claim 3 (depends on 1)

The method of claim 1, wherein the facade includes a DNS name and port resolving thereto that are unknown to the client application.

### Claim 4 (depends on 3)

The method of claim 3, wherein when the client application connects to the facade, the client application believe it is connected to the corporate application.

### Claim 5 (depends on 1)

The method of claim 1, further comprising volumetric logging, by the facade at the secure access cloud PoD, of the secure communication session.

### Claim 6 (depends on 1)

The method of claim 1, further comprising auditing, by the façade at the secure access cloud PoD, of the secure communication session.

### Claim 7 (depends on 1)

The method of claim 1, further analyzing and modifying, by the facade at the secure access cloud PoD, a request or a response of the secure communication session.

### Claim 8 (depends on 1)

The method of claim 1, further analyzing and delaying, by the facade at the secure access cloud PoD, a request or a response of the secure communication session.

### Claim 9 (depends on 1)

The method of claim 1, further analyzing and dropping, by the facade at the secure access cloud PoD, a request or a response of the secure communication session.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
identifying, by the facade at the secure access cloud PoD, a sensitive command about to be executed by the client application, and
sending, by the facade at the secure access cloud PoD, a notification to an IT administrator regarding the sensitive command.

### Claim 11 (depends on 1)

The method of claim 1, wherein the secure communication session employs Hypertext Transfer Protocol Secure (HTTPS), Secure Shell (SSH), Remote Desktop Protocol (RDP), Secure Copy Protocol (SCP), or SSH File Transfer Protocol (SFTP).

### Claim 12

A computer-implemented method comprising:
receiving, at a secure access cloud point of delivery (PoD), from an SSH client application on a client device, a request to access a corporate SSH server that is deployed in a corporate datacenter, wherein the secure access cloud PoD is isolated from the corporate datacenter;
creating, at the secure access cloud PoD, a facade representing the corporate SSH server, wherein the façade replicates, at least in part, portions of the corporate application;
forwarding, from the facade at the secure access cloud PoD, to a connector that is also deployed in the corporate datacenter, the request to access the corporate SSH server; and
brokering, by the connector and the facade at the secure access cloud PoD, authentication of a user, authorization of access by the user, and a secure communication session between the SSH client application and the corporate SSH server via the facade, with no corresponding agent being installed at the client device, and with the SSH client application being unaware that the secure communication session is brokered by the connector and the facade at the secure access cloud PoD, wherein brokering the secure communication session between the client application and the corporate SSH server includes establishing a communication channel between the facade at the secure access cloud PoD and the connector, and wherein communication between the client application and the corporate SSH server is conducted via the facade at the secure access cloud PoD and the connector at the corporate datacenter over the communication channel.

### Claim 13 (depends on 12)

The method of claim 12, wherein a public certificate authority (CA) certificate is deployed on the corporate SSH server.

### Claim 14 (depends on 13)

The method of claim 13, wherein the corporate SSH server is configured to validate session certificates of the secure communication session.

### Claim 15 (depends on 13)

The method of claim 13, wherein no active agent is present at the corporate SSH server.

### Claim 16 (depends on 12)

The method of claim 12, further comprising causing, by the facade at the secure access cloud PoD, a certificate authority (CA) to generate a unique short-lived certificate for the secure communication session that has specific session parameters embedded therein.

### Claim 17 (depends on 12)

The method of claim 12, further comprising enforcing, by the facade at the secure access cloud PoD:
a local access policy to decide whether to provide access to the corporate SSH server;
specified authentication types; and/or
4-eyes access and operations approval.

### Claim 18 (depends on 12)

The method of claim 12, further comprising controlling, by the facade at the secure access cloud PoD:
specific shell commands;
output data;
Secure Copy Protocol (SCP) files; and/or
SSH File Transfer Protocol (SFTP) files.

### Claim 19 (depends on 12)

The method of claim 12, further comprising deceiving, by the facade at the secure access cloud PoD, a potentially malicious user by providing the potentially malicious user with false data and/or a false indication on a result of a performed operation.

### Claim 20 (depends on 12)

The method of claim 12, further comprising detecting and logging, by the SSH client application, sensitive information being input by the user to avoid the sensitive information being logged in an audit log by replacing the sensitive information with benign characters in the audit log.
