We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.

We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.

For more information around feature requests in the Cireson Community click here.

Regulator requirements field for SW Assets

On the SW Assets it would be of great benefit to have a field with multiple choices to select different regulations that the software falls under. These could be: ITAR / Personel Integrity / HealthCare / ExportLicense1 / ExportLicense2 / MilitaryLicense1 / etc. 
These regulatory requirements could be an entirely new class to make it easy to create views based on it and the fact that a SW could be connected to multiple variants. To have them connected as related CI's would be an acceptable setup even though a separate field would be preferable.. wink 

This to make it easy to identify which software that supports what of those, which may have effect on Change Management processes, audits, etc.
4 votes

Submitted · Last Updated

Comments

  • pzergerpzerger Partner Adept IT Monkey ✭✭
    edited September 2016
    Jon, while this is a perfectly legitimate request,  I fear this looks like an organizationally specific process. With that in mind, I think pursuing your own customization is probably the best path in this case. Thanks for taking time to make the request. Keep the feedback coming!
  • Jon_RunheimJon_Runheim Customer Adept IT Monkey ✭✭
    Ok, I understand, but are a bit worried.

    EU has in 2016 passed a personal integrity law that will apply on all companies within EU in 2018. The companies will have to keep track of all software that keep personal integrity data (which all companies have). They are obliged to manage this softwares accordingly or they will face incredible penalties (up to 4% of the total worldwide annual turnover of the preceding financial year).
    I would expect the possibility to track softwares that are affected by this and other similar upcoming laws as part of the default functionality for any ITAM tool.

    The new EU regulation is: The General Data Protection Regulation (GDPR) (Regulation (EU) 2016/679)
    https://en.wikipedia.org/wiki/General_Data_Protection_Regulation

    What are the Cireson take / solution on this upcoming scenarios? Any workaround with the current toolset that could make such a register / SW Asset view possible?

  • Jon_RunheimJon_Runheim Customer Adept IT Monkey ✭✭
    FYI - As of now, we have solved this temporarily by setting up licenses as "EU GDPR", "ITAR", etc.
    This, in combination with a custom type-projection (SWAssetHasLicense) way we can achieve the goal, even though in a not so nice manner..
    A custom class for Regulatory requirements would be the best solution. The similarities with licenses are fairly big (vendor = requirement source, Custodian, Targeted software, etc), but they should not be found in the same sections on the software asset forms or license views.. :/
Sign In or Register to comment.