Socreg: Protected Data Applications

A knowledge base article about Socreg: Protected Data Applications provided by the UC Berkeley IT Service Hub - Knowledge Portal

Table of Contents

Overview and Requirements
Key Terms and Definitions
PD Application Form Attributes
Components and Scope Definitions

Overview

Security Contacts use Socreg to register Protected Data (PD) Applications—systems that handle, store, or transmit institutional data restricted by laws and policies. This information provides an inventory for security incidents and enables enhanced monitoring for the application's components.

Monitoring Note: Components registered within a PD Application receive prioritized vulnerability scanning and elevated threat detection. For details, see the Socreg FAQ on PD Monitoring.

Registration Requirements:

Mandatory: All systems with a Data Protection Level of P2 or higher must be registered. (See: Data Classification Standard).
Recommended: Registration for systems with an Availability Level of A3 or higher is highly recommended. (See: Availability Level Definitions).
Annual Review: Security Contacts must review registration information at least annually for accuracy.

Terms

Term	Definition
PD Application	Any IT system (application, service, or collection of devices) handling data classified as P2 or higher.
PD Services	Shared IT services (e.g., Berkeley IT-managed services) that can be components of multiple PD Applications. Each service is managed by its own Security Contact.
Subnets / IPs	Blocks of IP address space or specific network addresses assigned to the application.
Offsite Hostnames	Fully Qualified Domain Names (FQDN) in the `berkeley.edu` domain that resolve to non-Berkeley IP addresses.
Devices	Physical hardware identified by Ethernet MAC address.
Security Contact	The group that registered the specific components. See: KB0015397 - Security Contacts.
PD Application Owner	The Security Contact responsible for maintaining the PD Application's overall registration.

PD Application Attributes

The following fields are required when registering a PD Application in Socreg:

Form Field	Expected Input	Example
PD Application Name	A friendly, human-readable name.	My Research Web App
Description	Function of the app, data types handled, and any acronyms.	Stores student SSNs for enrollment purposes.
Protection Level	The highest classification of data handled (P2–P4).	P3
Availability Level	Operational impact if the system goes down (A1–A4).	A3
Application URLs	Web URLs or Windows file share paths used to access the system.	`https://app.berkeley.edu`
Record Quantity	Approximate number of records handled.	> 5000

PD Application Components

PD Applications can include Cloud Accounts, Subnets, IP Addresses, Subdomains, Offsite Hostnames, and Devices. These components can be registered to any Security Contact, allowing multiple groups to collaborate on a single application registration.

Component Scope Definitions

Scope	Usage
Institutional Device	Servers, credential stores, and large databases of Protected Data.
Privileged Access Device	Administrative endpoints used to manage Institutional Devices. This includes P4 Individual Workstations. See: KB0015628 - Registering P4 Workstations.

Please contact socreg@berkeley.edu for any questions or additional support.