Socreg FAQs

A knowledge base article about Socreg FAQs provided by the UC Berkeley IT Service Hub - Knowledge Portal

Can I self-register Fixed IP address assignments?

Department and Group Security Contacts can register devices for Fixed IP address assignment – where a device always gets the same IP on its primary subnet, but a Dynamic IP on any other subnet – provided that the Security Contact has a registered subnet, with an available IP address space, and a registered subdomain.

For details about registering devices for Fixed IP address assignment, please review the "Devices" page in the Socreg documentation.

Does the application support IPv6?

Yes, Socreg supports IPv6.

How are security notices routed?

Security notices are routed based on the registration information in Socreg.

For example, if an IP address has a registered Security Contact, the security notice is sent to that Security Contact, but if there is no specific IP address registration, then the notice is sent to the Security Contact that registered the subnet that contains the IP Address. Notices will also be sent to:

How do I register P4 workstations as Protected Data Applications in Socreg?

Please see Instructions for Registering P4 Workstations in Socreg for step-by-step instructions.

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:

Note: This setting is different than the ‘Receive FYI messages’ setting.  FYI messages are set per unit Security Contact and are FYI messages about the Security contact and its assets.

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 xyz.berkeley.edu and another security contact B claims subnet a.b.c.0/24 and there is a set of hostnames defined in DNS:

a.b.c.11   h1.xyz.berkeley.edu

a.b.c.12   h2.xyz.berkeley.edu

a.b.c.13   h3.xyz.berkeley.edu

security contact A and B will each get a message suggesting that the IP addresses be transferred from B to A.

Either security contact can initiate the transfer: Security contact A can 'request to take'; B can 'request to give'.

If the other party agrees and approves the transfer then B ends up with the subnet and A has 3 individual IP records out of that subnet because of its subdomain registration.

Remember: Socreg does not automatically make the transfer because there may be alternate solutions to resolve the discrepancy.  In the above example, security contact A could relinquish the IP addresses, or have their DNS hostname changed to something not in the xyz subdomain.

You are receiving this "IP address to transfer" message so that you can choose the best solution.

What are the types of email generated by Socreg? Can I opt out from receiving any/all of them?

There are three types of email generated by Socreg:

  1. FYI emails: These emails are rolled up into a single digest which is sent once per week. Users can opt-out of receiving the digest by setting "Receive FYI digest" to “off”. However, at least one member of the Security Contact should continue to receive them.  Some FYI emails are sent immediately, for example when a PD Application or one of its components is modified.
  2. Notices about Access or Asset Requests.  Others may submit a request in Socreg for:

Or an asset:

Notifications are sent when the request is made and will repeat weekly until either approved or denied in Socreg.  

3. Notices to "outside" entities (i.e., ISO ticketing system, DNS Administrator, or IT Policy): These are initiated by Socreg backend processes or sometimes by Socreg users and are copied to the Security Contact’s membership.For example, when a request is made for a new Department Security Contact, the request will go to ISO and we will conduct an intake process before creating the Department Security Contact.

What email address should I use for my Security Contact?

A Security Contact has one email address that is used to receive security notices. The email address should reach multiple people either via a listserv, group address, or, ideally, a CalNet Special Purpose Account so that security incidents involving a department or group's IT Resources receive prompt attention. SPAs are CalNet IDs that can be shared by multiple users for collaborative purposes and are recommended for this purpose. See CalNet's SPA page for information and instructions on setting up a SPA account for a Security Contact to receive security notices.

What is the process if another Security Contact is non-responsive when I want to claim or transfer something immediately?

Contact the Information Security Office at: socreg@berkeley.edu

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 Contact created just for that shared responsibility might be the best solution.