Gaining unified control over vulnerabilities has improved governance but pricing and support need workThe market price is slightly high. The pricing should be a little lower because this is a SaaS-based product. Everyone using ServiceNow might be getting many modules, but the overall module cost becomes high with license consumption one by one. I personally see that if ServiceNow is to grow over the next decade, they need to work on the pricing part. Cheap providers are emerging, and in the age of AI, it is evident that the chatbot and the virtual agent features, which are prominent features of ServiceNow, could be completely compromised and replaced by people choosing other tools. If ServiceNow develops a strategy to lower the price and increase the customer base, it could help ServiceNow to grow for another decade. I encountered one issue in ServiceNow Security Operations. The different tools, for example, Tenable and TVM, discovered vulnerabilities that had very limited information when imported. However, the same vulnerabilities from different sources, the TVM and Tenable, had shorter descriptions than what was present in the common vulnerabilities or CVE. If this depends on the implementer, such as Tenable or how other security operations implement them, the text was very limited. Customers were asking questions about why this was happening and if ServiceNow was working properly. The vulnerability information should be updated and the common text should be displayed every time, regardless of how many different tools are used for integration. The vulnerability database should be consistent when it comes to the description to avoid confusion for customers implementing it for the first time. This is an improvement that ServiceNow can make.
