CodeLogic Installation Requirements

The system requirements for installing and using CodeLogic are listed below.

General Prerequisites

  • Internet access.

    NOTE

    The CodeLogic Server must have access to the Internet on ports 80 and 443 (http and https, respectively) for initial installation, license verification and upgrades.

  • A Linux system for the CodeLogic Server.

    NOTE

    A devoted system is preferred. The system should NOT be in a production environment. The system should examine applications in a staging or test environment.

  • Familiarity with basic system administration tasks, such as editing configuration files.

  • Root (sudo) or administrator access to the CodeLogic Server system.

  • Root (sudo) or administrator access to any system upon which the agent will be installed.

  • Read credentials to any database to be monitored.

    NOTE

    Only the schema is accessed, no data will be read.

  • A secure environment. Security

Minimum Requirements for Servers and Agents

NOTE

Required Linux packages, such as Open JRE 11 and docker-compose, if not installed, will be installed during installation. A Windows JRE is included for the Java Agent on Windows. EXCEPTIONS: agents running CentOS6 and servers running on RHEL-based systems may require installations of software that are not available in default software repositories, such as Docker Engine and Docker Compose. Similarly, .NET must be installed prior to installing the .NET agent.

Package Platform (x86_64) Logical Processors Required Disk Space Memory Required Packages
CodeLogic Server (Debian-based)

Ubuntu 18.04 LTS

4

30 GB
(20 GB Free)

16 GB

docker, docker-compose
CodeLogic Server (RHEL-based)

Fedora

4

30 GB
(20 GB Free)

16 GB

docker-ce (>=20.10)1
CodeLogic Java Agent

Amazon Linux 2

CentOS 6

Debian 10

Fedora 32

Red Hat Enterprise Linux 7.9

Ubuntu 18.04 LTS

Windows 10 1909

Windows Server 2019

2

100 MB Free

1 GB OpenJRE 11
CodeLogic SQL Agent

Amazon Linux 2

CentOS 6

Debian 10

Fedora 32

Red Hat Enterprise Linux 7.9

Ubuntu 18.04 LTS

Windows 10 1909

Windows Server 2019

2

60 MB Free

1 GB OpenJRE 11
CodeLogic .NET Agent

Windows 10

Windows Server 2012R2

Windows Server 2016

Windows Server 2019

2

5 GB Free

4 GB

.NET Core 3.12

Max Storage Used

Installation

Operating System Common File System Different File System

Fedora 34/RHEL 8.5

9.5 GB

/opt 6.4 GB

/var 6.9 GB

/tmp 50 MB

Ubuntu 20

8.3 GB

/opt 6.0 GB

/var 7.7 GB

/tmp 50 MB

Upgrade

Operating System Common File System Different File System

Fedora 34/RHEL 8.5

7.3 GB

/opt 5.6 GB

/var 5.7 GB

/tmp 25 MB

Ubuntu 20

3.4 GB

/opt 5.3 GB

/var 2.7 GB

/tmp 25 MB

Security

Certificates

NOTE

A valid (Transport Layer Security) TLS certificate must be installed prior to installing agents.

Information about applications and databases is collected by the agent and sent as metadata to the CodeLogic Server. No actual data is ever sent. The metadata does not leave the network, it is only sent from the agent to the CodeLogic Server. However, even metadata should be protected.

To prevent the metadata from being intercepted in transit, CodeLogic requires (Secure Sockets Layer/Transport Layer Security) SSL/TLS for data encryption, data integrity and authentication.

Installing SSL certificates is beyond the scope of these instructions.

However, we assume:

  • The CodeLogic Server system has a signed digital certificate installed.

  • The system upon which the CodeLogic Agent is installed has the corresponding public certificate installed.

The installer allows insecure communications to be configured but this should only be used for testing purposes on systems that do not contain any sensitive data. It is not recommended but, if this option is chosen during installation, no certificate will be required, and http will be used instead of https.

The signed TLS certificate on the CodeLogic Server should not be a wildcard certificate. In the event of a security breach, all hosts using the certificate become vulnerable.

A self-signed certificate is provided but is only used for proof of concepts. It cannot be used for secure communication between agents and the CodeLogic Server.

Firewall

Internet access is needed only for the CodeLogic Server installation (and upgrades). The repository key and software are downloaded using http or https (port 80/443).

If there is a firewall enabled on the systems running the agents, it should allow http or https access to the CodeLogic Server.

Administrator Accounts

A default administrator account is seeded. We recommend changing the default password after installation.

Similarly, each agent uses a default account and password. The agent configuration file is only readable by root.

Password Management

CodeLogic uses FusionAuth for password management.

If a CodeLogic admin goes to Admin > Users, they have to reauthenticate to get into the FusionAuth administrative console. From there, they would go to Tenants > Password and set a policy.

Documentation on setting the policy is available from FusionAuth.

https://fusionauth.io/docs/v1/tech/core-concepts/tenants/#password

CORS is disabled by default. For a more secure system, you should enable CORS in FusionAuth once a final host name has been established.

For more information on CORS please refer to the FusionAuth website.
https://fusionauth.io/docs/v1/tech/reference/cors/