Questions regarding ITOM.
- 7 Topics
- 6 Replies
When using assystITOM v5006-5, a security alert may be raised referring to the presence of the file log4j-1.2.13.jar
Environment: assyst ITOM - v5006-5Knowledge Area: How to?Audience: ALLSource: IFS assyst ITOM SupportVerified: Yes DescriptionWhen using assystITOM v5006-5, a security alert may be raised referring to the presence of the file log4j-1.2.13.jar. Resolution/AnswerThis refers to the named file located at the following two locations:ConsoleManagement\lib\hibernateConsoleManagement\lib\log4j The originally encountered vulnerability with log4j-1.2.13 has been resolved as we are now using log4j v2. However, the referenced file has not been fully removed.If using assystITOM v5006-5 and a security alert referring to the above mentioned file is encountered, to resolve follow the procedure below:Stop the SapphireIMS Service on the affected server. Delete the file log4j-1.2.13.jar from the two locations referenced above Start the SapphireIMS Service Additional Information This should only be performed when using assystITOM v5006-5. Earlier versions require an upgrade to the latest release of ass
We’re working with an organisation that’s interested in the ITOM suite. We have a question raised during a technical deep dive relating to the SKU information we keep in ITOM against each Software License. In ITOM, we have the fields for SKU information (SKU code, downgrade rights, software assurance etc) – however none of this is auto-populated from the current version of the Software Dictionary.In the short-term, has anyone created a reconciliation report to address this or experienced a way to get this SKU information into ITOM without the manual effort?Thanks
We need to add feature for creating or exporting report for Critical-Important-Normal deployed Patches,This is a major need and feature we need to so we can categorize or filter the type of patches that we deployed, without this feature its not possible to identify the severity of the deployed patches
Hello Techs,We have a requirement where ITOM agent password should be in encrypted format and should not be visible by any means.Encryption of the password is to be enabled across the entire installation process. Reason being, the server does not have the password in the encrypted format currently which indeed a vulnerability by all the means and has been picked up by the Cyber Security folks.We need the password to be in encrypted format in order for us to make sure it does not show up anywhere while the entire process takes place.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.