A DUAL-POLARIZED TAPERED SLOT ANTENNA ARRAY WITH REDUCED PROFILE HEIGHT

IT asset management is the foundation for building an effective vulnerability management process.Without an understanding of the IT assets under control, it is technically impossible to start building avulnerability management process. With an existing IT asset management process in place, one of thetasks that is essential to vulnerability management is to uniquely name software as an asset. This unambiguousnaming allows the software and its vulnerabilities to be identified without actively scanning ITinfrastructure nodes, but only by interacting with the IT asset management system. Technically, this approachcan be called “passive vulnerability detection,” but it is extremely labor-intensive to implementusing existing naming systems. In order to make the possibility of passive detection more realistic, theauthors propose to create a common foundation by forming a conceptual scheme and then creating a systemof standardized naming and identification of software, the regulation of which will be centralized atthe state level. As part of the review of existing software naming systems, attention is paid to CPE problemsboth on the part of on-site specialists, namely obtaining CPE identifiers and translating softwareinformation into a CPE identifier, and on the part of a vulnerability data aggregator, namely obtainingvulnerability information via a CPE identifier. The problems of CPE application, as well as the problemsof interaction with vulnerability data aggregators from unfriendly countries, discovered in the course ofthe research form the prerequisites for the formation of a national system for state regulation of softwarenaming and identification, which will eliminate the problems of existing software naming systems. In conclusion,advantages of the national system of software naming and identification are given in case of itscreation and use in real conditions by all participants of the vulnerability management process