Create regulatory change management

[Munny1]

@Ankur Bawiskar @Community Alums 

1. From the RSS feeds 

[Community Alums · Accepted solution]

Hi @Munny1 ,

By design, RSS feeds will be housed in "sn_grc_rss_feed_request_response" Table itself.

It's not recommended to use Alerts for RSS feeds, As an alert is something that needs your attention but doesn't necessarily require an immediate response. The main purpose of alerts in incident response systems is to get the right person's attention to investigate a potential issue related to a service that they own or support. Alerts need to happen close to real-time as if the issue is validated restoration needs to happen as quickly as possible to keep MTTD (mean time to detect/diagnose) and MTTR (mean time to resolve) low. Alerts are primarily informational qualified events where predefined system logic indicates an issue that a human need to validate and decide if an incident is required. Only your technical on-call SME team is working on the alerts. Alerts are qualified events because events are constantly collecting and tracking data related to a metric and monitoring, such as latency, errors, saturation, etc. Whereas events are simply ‘raw data’ independent of the context of that data being good or bad. Alerts are a qualified set of these events deemed bad, associated with a notification to inform the technical team.  

Now if you want to work on this custom approach as per your requirement, then you have do a lot of things, you need deactivate "Pull RSS Feed to Regulatory Change" Flow, Feed Sources should be removed from "sn_grc_rss_feed_source" table.

So it's not recommended to proceed with above requirement.

[Munny1]

Hi @Community Alums ,

Can we fetch only which are relevant regulations.Because there are large amount of data .either from RSS feed or Thomson retures .

Because there are 100 of regulations but it 70 to 80 regulations are relevant