Skip Headers

Agile Product Lifecycle Management Security Guide Release 9.3.3 E39280-01 |
| Contents

Previous | Next |

# 3 Overview of Security Fundamentals

This section describes the Security Fundamentals.

## 3.1 Basic Security Considerations

The following principles are fundamental to using any application securely.

### 3.1.1 Keep Software Up-To-Date

One principle for good security practice is to keep all software versions and patches up-to-date. To ensure that you have the most current and updated Agile PLM software for the latest version, regularly check the updates page.

### 3.1.2 Restrict Network Access to Critical Services

Keep both the Agile PLM application and the database behind a firewall. In addition, place a firewall between the middle-tier and the database. The firewall provides assurance that access to these systems is restricted to a known network route, which can be monitored and restricted, if necessary. As an alternative, a firewall router substitutes for multiple, independent firewalls.

If you cannot use firewalls, then configure the TNS Listener Valid Node Checking feature (it restricts access based upon IP address). Restricting database access by IP address often causes application client/server programs to fail for DHCP clients.

To solve this problem, use any of the following:

- static IP addresses

- software VPN

- hardware VPN

- software VPN and hardware VPN

- Windows Terminal Services or its equivalent

### 3.1.3 Follow the Principle of Least Privilege

The principle of least privilege states that users should be given the least amount of privilege to perform their jobs. Over-ambitious granting of responsibilities, roles, grants, etc., especially early on in an organization's life cycle when people are few and work needs to be done quickly, often leaves a system wide open for abuse. User privileges should be reviewed periodically to determine relevance to current job responsibilities.

### 3.1.4 Monitor System Activity

System security stands on three legs: good security protocols, proper system configuration and system monitoring. Auditing and reviewing audit records address this third requirement. Each component within a system has some degree of monitoring capability. Follow audit advice in this document and regularly monitor audit records.

### 3.1.5 Keep Up To Date on Latest Security Information

Oracle continually improves its software and documentation. Check this note yearly for revisions.