New Security System - TPSCRM ¶

• How to migrate security system to TPSCRM?
• How to fix the security issue on TPSCRM?
  • File a CDETS
  • Backend Change
  • Add/Edit components in Corona
  • Update CDETS Status
• Reference

How to migrate security system to TPSCRM? ¶

We need to migrate the GSS security system from IPCentral to TPSCRM according to this reminder.

Migration can be done according to the following steps:

1. Export the components list from IP Central.
2. Import components from IP Central to Corona.
3. Then we can see our project on TPSCRM.

How to fix the security issue on TPSCRM? ¶

Note: Generally speaking, when GSS has security issues, gss-devops will receive email reminders from ciam-support. (like the screenshot above) Then you can follow these steps below to solve.

File a CDETS ¶

1. You can click "Vulnerability Report" in Corona BOM report and check all vulnerable components.

2. You can file CDETS for these vulnerable components. You can refer to https://cdetsng.cisco.com/webui/#view=CSCvv39895 or others. (Project: CSC.csg, Product: gss)

Backend Change ¶

1. Generally speaking, we need to upgrade the version of the backend package. For example, in this example, we need to update the version of dom4j.

2. We can find this package in backend pom.xml file and update the package version following the alert instruction. (Usually need to update to the latest version)
   

3. We need to ensure the normal build of the backend project in local and dev, and push to stage and prod.

Add/Edit components in Corona ¶

We can refer to Reference[5].

Update CDETS Status ¶

We should update CDETS status to 'resolved'. (it's filed in File a CDETS above)

Reference ¶

1. Corona Quick Start Guide
2. Import from IP Central using IP Central Export to CSV file
3. IP Central Import
4. Importing IP Central Blackbox into Corona
5. Adding and deleting Components