socreg - asset registration portal

Basic Socreg Functions and Use Cases

The following instructions explain how to establish a Security Contact and register assets to receive security notices about those assets.

Establish a Security Contact by using the sidebar item Asset/Access Requests.

If you are not a member and a Security Contact exists, you may request to join the membership by selecting “Request membership” from the drop-down menu. Someone in the Security Contact will have to approve your request.

If there is not a Security Contact for your department, you may...

Registered Assets

Accurate and complete registration of assets lets the Information Security Office (ISO) notify your department of problems and security risks. Security Contacts can register or claim network assets including: Cloud Accounts, Subnets (as defined by the Network group), IP addresses, Subdomains, Offsite hostnames, Devices, and Protected Data Applications and Services.

Users accessing from an off-campus IP address, or while connected to CalVisitor, will need to use the...

Socreg - Asset Registration Portal


Socreg is a self-service asset registration portal developed by the Information Security Office (ISO) to help campus departments and their Security Contacts maintain the registration of network assets and Protected Data, and to meet Policy requirements.

A Security Contact is a group of authorized members who register IT Resources and receive security notices involving those resources. UC Berkeley’s...

Protected Data Applications

Please note: If you are connecting to from OFF CAMPUS you must first connect to the campus VPN to access the portal.

Security Contacts can register Protected Data (PD) Applications or systems that handle, store, or transmit institutional data restricted by laws and policies. This registration...

Offsite Hostnames

The Information Security Office reviews and approves all new offsite hostnames before the campus DNS Administrator can create the necessary DNS records.

How to register a new offsite hostname: Log into with your CalNet ID Click on the appropriate Unit Security Contact. (If you don't see any Unit Security Contact names, click "My Assets" and the "New Offsite Hostname" button.) Click on the "Offsite Hostname" button on the left And then Click "New Offsite Hostname"

Note: an individual can start the request but during the approval process the...

How Do I Update My Socreg Profile Settings?

To change your profile settings in Socreg, log in and click your name in the top bar and then click ‘Settings’. Current options are:

Receive Release Email - this toggles whether or not you would like to receive the Socreg release notifications.

Note: This setting is different than the ‘...

Socreg Releases

As new software releases are deployed and the Socreg application is updated, information about the software releases is posted to the Socreg Releases Google Doc (CAS Authentication required to access).

Release information is also sent to admin membership of unit Security Contacts.

Why can’t two Security Contacts share the same subnet? We both have IP addresses on the subnet.

Overlap is not allowed in Socreg. If two departments share a subnet, the department who claims the most IP addresses for that subnet will get the entire subnet. The other department will get individual IP addresses.

Additionally, one Security Contact will register and be primarily responsible for an IP address, although other Security Contacts may also receive security notices for that IP address.

For complicated situations, e.g., where two different groups are responsible for systems on a subnet, a Security...

I've received an "IP address to transfer" message.

Here we explain what it means and what you need to do.

You've received the message because Socreg has encountered a mismatch between the security contact that claimed an IP address (individually or by subnet) and the security contact that registered a subdomain.

(Note: In Socreg the assignment of a subdomain enables the transfer of IP address responsibility to the right party, but does not assign security contact responsibility).

For example, if security contact A registers a subdomain and another security contact B claims subnet a.b.c.0/24 and there is a set of hostnames defined...