Regulatory feeds are an aggregation of different regulatory events
and documents that are sourced from multiple regulatory intelligence providers in different
formats. The Regulatory Change Management application transforms and maps the feeds.
The application provides the information in regulatory feed tables.
The Regulatory Change Management life cycle starts with the regulatory feed record.
Each regulatory feed record contains metadata that helps stakeholders to translate the
changes, create an action plan, and implement actions to comply with the regulatory changes.
Feeds and user roles
Different types of feeds are displayed under the Regulatory Feeds module
in the Regulatory Change Management application. The following table provides
information about the feeds displayed in the module, the user roles that can perform the
actions, and a description of the feed states. An assigned feed is a feed that is assigned
to a user or coordinator.
Table 1. Regulatory feeds, user roles, and description
| Fields displayed in the module |
User roles that can perform the actions |
Description of the states |
| All Assigned Feeds |
- sn_grc_reg_change.admin
- sn_grc_reg_change.manager
This view is also available to users with the sn_grc_reg_change.user role.
Those users can view only the assigned feeds and not all the feeds in the
system. |
All feeds in the system that have
been assigned to a coordinator or sn_grc_reg_change.user. The
Coordinator field for these feeds has a value assigned to
it. The feeds can be in Applicable or Deferred state. |
| Unassigned Feeds |
- sn_grc_reg_change.admin
- sn_grc_reg_change.manager
|
All feeds in the system that are not yet assigned to a coordinator. The
Coordinator field for these feeds is empty. |
| New Feeds |
- sn_grc_reg_change.admin
- sn_grc_reg_change.manager
- sn_grc_reg_change.user
|
All assigned feeds in the system that are in the
New
state. |
| Deferred Feeds |
- sn_grc_reg_change.admin
- sn_grc_reg_change.manager
- sn_grc_reg_change.user
|
All assigned feeds in the system that are in the
Deferred
state. |
| Impact Assessment Feeds |
- sn_grc_reg_change.admin
- sn_grc_reg_change.manager
- sn_grc_reg_change.user
|
All assigned feeds in the system that are in the
Impact
Assessment state. |
| In Progress Feeds |
- sn_grc_reg_change.admin
- sn_grc_reg_change.manager
- sn_grc_reg_change.user
|
All assigned feeds in the system that are in the
In
Progress state. |
| Closed Feeds |
- sn_grc_reg_change.admin
- sn_grc_reg_change.manager
- sn_grc_reg_change.user
|
All assigned feeds in the system that are in the
Closed
state. |
Types of feeds and associated regulatory tasks
The following table provides information about the types of feeds and their associated
regulatory tasks.
Table 2. Types of feeds and related tasks
| Types of feeds |
Description |
Associated regulatory tasks |
| Regulatory events |
Feeds of regulatory event type signify alerts. They
provide updates to the news and provide insights on regulatory changes. The
default value for the feeds is a regulatory event. |
A Regulatory Change Task is created whenever a user with
the sn_grc_reg_change.user role reviews a feed of regulatory event type and then
marks it as applicable. A Regulatory Change Task is used to evaluate the changes
and to update the GRC objects, such as policies, controls, and risk statements in
the library. |
| Source documents |
Feeds of source documents type signify changes to the citations or to control
objectives. |
A Source Document Import Task is created whenever a user with the
sn_grc_reg_change.user role reviews a source document type of feed and then marks
it as applicable. A Source Document Import Task is used to update an existing
citation or to insert a new citation that is received from the provider into the
regulatory library. |
Table cleaners for regulatory feeds
The feed records that are in the Not Applicable state must be cleaned at
regular intervals. The Regulatory Change Management application provides table
cleaners for cleaning the feed records automatically. Users specify the time and frequency
for the cleanup activity.
Similarly, registry file records that have been processed can be cleaned at specified time
intervals.
