Filetype Excel XLS | Posted on 07 Jul 2022 | 3 years ago
Authentication
digital resources
250x Filetype XLS File size 0.16 MB Source: www.loc.gov
Sheet 1: Base Information
| App ID | ||||||||||||||||||
| Application Name | ||||||||||||||||||
| Secondary Application Name (a.k.a.) | ||||||||||||||||||
| Application Description | ||||||||||||||||||
| Application URL | ||||||||||||||||||
| Implementation Date | ||||||||||||||||||
| Software Class | Application | |||||||||||||||||
| Application Type | ||||||||||||||||||
| Approved COOP Tier | ||||||||||||||||||
| Survival Guide (date of last update) | ||||||||||||||||||
| Application Category | ||||||||||||||||||
| Vendor | Leave this field BLANK | |||||||||||||||||
| Product Name | Leave this field BLANK | |||||||||||||||||
| Responsible R&D Organization | ||||||||||||||||||
| Responsible R&D Manager | ||||||||||||||||||
| System Owner (SO) | ||||||||||||||||||
| SO Organization Code | ||||||||||||||||||
| Designated Approval Authority (DAA) | ||||||||||||||||||
| Information System Security Officer (ISSO) | ||||||||||||||||||
| Backup ISSO | ||||||||||||||||||
| SU Lead Tester | ||||||||||||||||||
| R&D Tech Lead | ||||||||||||||||||
| Backup R&D Tech Lead | ||||||||||||||||||
| Other R&D Support Staff | ||||||||||||||||||
| Other SU Support Staff | ||||||||||||||||||
| DIMS ID | Leave this field BLANK | |||||||||||||||||
| DIMS Application Name | Leave this field BLANK | |||||||||||||||||
| C&A ID | Leave this field BLANK | |||||||||||||||||
| C&A Application Name | Leave this field BLANK | |||||||||||||||||
| Application Name on EA | Leave this field BLANK | |||||||||||||||||
| Client Applications | Client ID 1 | Leave this field BLANK | ||||||||||||||||
| Client ID 2 | Leave this field BLANK | |||||||||||||||||
| Client ID 3 | Leave this field BLANK | |||||||||||||||||
| Client ID 4 | Leave this field BLANK | |||||||||||||||||
| Client ID 5 | Leave this field BLANK | |||||||||||||||||
| Application Subsystems | Subsystem 1 | Leave this field BLANK | ||||||||||||||||
| Subsystem 2 | Leave this field BLANK | |||||||||||||||||
| Subsystem 3 | Leave this field BLANK | |||||||||||||||||
| Subsystem 4 | Leave this field BLANK | |||||||||||||||||
| Subsystem 5 | Leave this field BLANK | |||||||||||||||||
| Subsystem 6 | Leave this field BLANK | |||||||||||||||||
| Subsystem 7 | Leave this field BLANK | |||||||||||||||||
| Subsystem 8 | Leave this field BLANK | |||||||||||||||||
| Subsystem 9 | Leave this field BLANK | |||||||||||||||||
| Subsystem 10 | Leave this field BLANK | |||||||||||||||||
| Application Tools | Programming/Scripting Languages Used | Language1 | ||||||||||||||||
| Language2 | ||||||||||||||||||
| Language3 | ||||||||||||||||||
| Lanauage4 | ||||||||||||||||||
| Lanauage5 | ||||||||||||||||||
| Lanauage6 | ||||||||||||||||||
| Lanauage7 | ||||||||||||||||||
| Lanauage8 | ||||||||||||||||||
| Lanauage9 | ||||||||||||||||||
| Lanauage10 | ||||||||||||||||||
| Database Platform | Name | |||||||||||||||||
| Version | ||||||||||||||||||
| Development Tools | Tool Name1 | |||||||||||||||||
| Tool Name2 | ||||||||||||||||||
| Tool Name3 | ||||||||||||||||||
| Tool Name4 | ||||||||||||||||||
| Tool Name5 | ||||||||||||||||||
| Tool Name6 | ||||||||||||||||||
| Tool Name7 | ||||||||||||||||||
| Tool Name8 | ||||||||||||||||||
| Tool Name9 | ||||||||||||||||||
| Tool Name10 | ||||||||||||||||||
| Search Engine | Name | |||||||||||||||||
| Version | ||||||||||||||||||
| Reporting Tool | Name | |||||||||||||||||
| Version | ||||||||||||||||||
| Hosted Location | ||||||||||||||||||
| Hosting Vendor | Leave this field BLANK | |||||||||||||||||
| Governance Class |
| Data Dictionary | |||||||
| Master Application List - Base View | |||||||
| Column Name | Description | Data Type | Data Source | Data Format | Data Values | Update Frequency | Method |
| App ID | The unique identifier for each application in the Application Portfolio | Numeric [Key] | This value is a sequential number assigned by the Application Portfolio Administrator upon receipt of the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | 99,999 | 1 to 99,999 | Field will never be updated or changed. | NA |
| Application Category | Application Software is broken into multiple application categories which describe how the application components are implemented between the Client and the Server. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Client/Server - the application has components on both a Server and a Client (e.g., workstation); Standalone (a.k.a., desktop application) - the application has no Server components, all components reside on the Client; Web - the application has no Client components, all components reside on the Server (i.e., only a browser is needed on the client) and performs 1 or more business functions; Site Collection - the application has no Client components, all components reside on the Server (i.e., only a browser is needed on the client) but differs from a Web application in that it is a composite of static and/or dynamically generated content/information focused on a particular topic/subject area, it's only purpose is to facilitate the finding, accessing and display of content/information; and Mobile - the application has components on both a Server and a Client but the Client hardware the application was specifically designed for is a mobile device (e.g., iPad or iPhone) | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| Application Description | A brief paragraph describing the primary purpose and/or key functions of the application. | Memo | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Various | Annual | APM Data Sheet (Intranet Form) | |
| Application Name | The primary name used to refer to a particular application. In the case where an application has identified subsystems the Application Name will be composed of the abbreviation for the parent application, followed by a dash, followed by the name of the subsystem. | Alphanumeric | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Various | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| Application Name on EA | The name of application as it is listed on the Enterprise Architecture (EA) Application Listing | Alphanumeric | Enterprise Architecture Application Listing | Various; NOTE: The application name on the EA Application Listing should match the application name in the portfolio. | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| Application Type | An application can be 1 of 3 types depending on who developed the application. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | In-House - the application was developed using government staff in whole or in part, COTS - the application is commercially available to be purchased from an outside vendor; Contractor - the application was developed solely by an outside vendor for the specific use of the Library, Open Source - the application is commercially available for free. | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| Application URL | The Internet address to the application's home/log in web page. | Alphanumeric | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Various; this field will only have a value when Application Category = Web or Site Collection | Annual | APM Data Sheet (Intranet Form) | |
| Approved COOP Tier | The tier number assigned to the application. The tier helps determine the order in which applications are restored at the Alternate Computing Facility when the COOP is activated. Tier 1 application are restored within 24 hrs, Tier 2 within 72 hrs and Tier 3 are restored as resources and equipment come available. | Numeric | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | 9 | 1, 2 or 3; Default value = 3 | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) |
| Back Up Information System Security Officer (ISSO) | The name of the government staff person who has been assigned as the applications' Back Up Information System Security Officer (ISSO). | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| Backup R&D Tech Lead (Escalation Tier 1) | The name of the R&D staff person who has been assigned as the backup to the R&D Tech Lead. This person is also usually assigned to respond to Footprint problems and work request tickets in the event the R&D Tech Lead is unavailable or does not respond to the ticket in a timely fashion. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; field will be blank if Type of Work = Liason Support or Liason & DBA Support; NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| C&A Application Name | The name of application as it is listed on ITSG's C&A Listing | Alphanumeric | ITSG's C&A Listing | Various; NOTE: The application name on the C&A Listing should match the application name in the portfolio. | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| C&A ID | Unique identifier assigned by the ITSG corresponding to the C&A for the application listed in the portfolio. | Numeric [Foreign Key] | ITSG's C&A Listing | ###-9999 | A two to four letter combination referring to a specific LOC Service Unit followed by a four digit number (e.g., CRS - 0001) | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) |
| Client ID 1-5 | Unique identifier assigned by the Workstation Configuration Control (WCC) team to desktop software associated with an application. | Alphanumeric | WCC Application Database | 9999 ####### | A four digit number followed by a two to seven character combination referring to a specific LOC Service Unit (e.g., 1234 OCIO); field will be blank if Application Category = Web, Site Collection or Mobile; NOTE: Up to 5 client IDs can be accommodated within the Base View. | Annual | APM Data Sheet (Intranet Form) |
| Database Platform - Name | The name of the database platform used with the application. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Oracle, Progress, SQL, Sybase, MySQL, Proprietary; NOTE: a value of Proprietary indicates that database functionality is integrated within the application. | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| Database Platform - Version | The version number of the database platform used with the application. | Numeric | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Variable | Various; field will be blank if the Database Platform - Name = Proprietary | Annually | APM Data Sheet (Intranet Form) |
| Designated Approval Authority (DAA) | The name of the government staff person who has been assigned as the applications' Designated Approval Authority (DAA). | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| Development Tools: Tool Name 1-10 | The name of the development platform or tools used to develop the application or used in developing any customization to a COTS product. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | APEX, Remedy, ccmMercury, Serena Business Mashups, MS SharePoint; blank indicates that a development platform was not used and/or Application Type = COTS | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| DIMS Application Name | The name of application as it is listed in DIMS | Alphanumeric | DIMS | Various; NOTE: The application name in DIMS should match the application name in the portfolio. | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| DIMS ID | Unique identifier within the Database Information Management System (DIMS) corresponding to the application listed in the portfolio. | Numeric [Foreign Key] | DIMS | 99,999 | 1 to 99,999 | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) |
| Governance Class | Indicates the number of SUs that use the application--1, some or all. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Distinct - application is used by a single SU or organization; Core - application is used by several SUs or organization but not all, Common - application is used by all SUs. | Annual | APM Data Sheet (Intranet Form) | |
| Hosted Location | The name of the data center where the application is hosted. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | MDC - Madison Data Center, ACF - Alternate Computing Facility, NLSBPH - Taylor Street Data Center, NAVCC - National Audio & Visual Conservatory Center Data Center, Fort Meade - Fort Meade Data Center or External | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| Hosting Vendor | The name of the vendor that is hosting the application | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Various; field will be blank unless Hosted Location = External | Annual | APM Data Sheet (Intranet Form) | |
| Implementation Date | The date the application was originally placed into production. | Date | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | mm/dd/yyyy or mm/yyyy | If this field is Blank it indicates the original implemenation date is unknown. | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) |
| Information System Security Officer (ISSO) | The name of the government staff person who has been assigned as the applications' Information System Security Officer (ISSO). | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| Other R&D Support Staff (cc'd on Footprint tickets) | The name of R&D staff who provide General O&M Support to the application in addition to the R&D Tech Lead. Staff listed are also cc'd on Footprint problem and work request tickets for the application. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; default value = None; NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| Other SU Support Staff (cc'd on Footprint tickets) | The name of SU staff who provide General O&M Support to the application. Staff listed are also cc'd on Footprint problem and work request tickets for the application. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; default value = None; NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| Product Name | The name given to the application by the company/vendor that sells the application on the commercial market. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Various; NOTE: This field is only completed when the Application Type = COTS. | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| Programming/Scripting Languages Used: Program Language 1-10 | The name of significant programming or scripting languages used to develop the application or used in developing any customization to a COTS product. | Alphanumeric | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Various; field will be blank if the Application Type = COTS; NOTE: Up to 10 programming or scripting languages can be accommodated within the Base View. | Annual | APM Data Sheet (Intranet Form) | |
| R&D Tech Lead | The name of the R&D staff person who has been assigned as the applications' Tech Lead. This individual is responsbile for coordinating all work associated with the application and is the application's primary Subject Matter Expert (SME). | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; field will be blank if Type of Work = Liason Support or Liason & DBA Support. NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| Reporting Tool - Name | The name of the reporting tool used to provide the reporting capabilities within the application. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Crystal or Proprietary: NOTE: a value of Proprietary indicates that reporting functionality is integrated within the application. | Annual | APM Data Sheet (Intranet Form) | |
| Reporting Tool - Version | The version number of the reporting tool used to provide the reporting capabilities within the application. | Numeric | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Variable | Various; field will be blank if the Reporting Tool - Name = Proprietary | Biannually | APM Data Sheet (Intranet Form) |
| Responsible R&D Manager (Escalation Tier 2) | The name of the R&D Division Chief who provides liason support to the SU of the application's System Owner. This person is also notified in the event the R&D Tech Lead and their backup do not respond to Footprint problems and work request tickets in a timely fashionigned. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; default is the name of the manager for the responsible R&D Organization; NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| Responsible R&D Organization | The responsible R&D Division within Office of the Chief Information Officer (OCIO) for supporting and/or managing the application. Usually the same Division that provides liason support to the SU of the application's System Owner. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | R&D, R&D LS&LL, R&D CRS, R&D DBA, R&D COP, R&D D&WI, R&D INF | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| Search Engine - Name | The name of the search engine used to provide the search capabilities within the application. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Ultraseek, Solr, Lucene, InQuery, or Proprietary: NOTE: a value of Proprietary indicates that search functionality is integrated within the application. | Annual | APM Data Sheet (Intranet Form) | |
| Search Engine - Version | The version number of the search engine used to provide the search capabilities within the application. | Numeric | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Variable | Various; field will be blank if the Search Engine - Name = Proprietary | Annual | APM Data Sheet (Intranet Form) |
| Secondary Application Name | The commonly used alias (a.k.a.) that refer to a particular application. | Alphanumeric | This value will more often than not come about overtime as users shorten or abbreviate the primary application name in conversations and/or correspondance. These secondary names will be entered by the Application Portfolio Administrator as they become known. | Various, If this field is blank it indicates there are no secondary application names | Annual | APM Data Sheet (Intranet Form) | |
| SO Organization Code | The organizational code of the government staff person who has been assigned as the applications' System Owner (SO). | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Various; NOTE: Valid values can be found on the approved list of organizational symbols published by the Library of Congress | Semi-annual | APM Data Sheet (Intranet Form) | |
| Software Class | Applications are classified into two (2) primary software classifications--Application Software and System Software. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Application - software that is not classified as "System" software; System - software such as Operating Systems, Utilities (e.g., Anti-virus), Compliers, Programming Languages, Development Tools (e.g., APEX and Remedy), Web Servers (e.g., Apache and IIS), Application Servers (e.g., Tomcat, JBoss, and WebLogic) | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| SU Lead Tester | The name of the Service Unit (SU) staff person who has been assigned as the applications' Lead Tester. This individual is responsible for coordinating SU testing associated with application recoveries, enhancements and upgrades. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| Subsystem1-15 | The name given to a significant functional component of an application. These components usually are implemented as a group but may be maintained and enhanced separately. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Various; blank indicates the application has no subsystems; NOTE: Up to 15 subsystem names can be accommodated within the Base View. | Annual | APM Data Sheet (Intranet Form) | |
| Survival Guide (date of last update) | The date the survival guide for the application was last updated. | Date | This value is obtained by conducting routine reviews of the application Survival Guides maintained by the Help Desk and pulling the date last modified from the document properties. | dd/mm/yyyy | If this field is Blank it indicates a Survival Guide does not exist for that particular application. A date of 01/01/2012 indicates that a Survival Guide exists but for some reason a date last modified can not be determined. | Semi-annual | APM Data Sheet (Intranet Form) |
| System Owner (SO) | The name of the government staff person who has been assigned as the applications' System Owner (SO). | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | last name, first name middle name | Various; NOTE: Middle Name is only entered when more than one person has the same first and last name. The middle initial can be used in lieu of the middle name if this does not result in a duplicate. | Semi-annual | APM Data Sheet (Intranet Form) |
| Vendor | The name of the company/vendor that sells the application on the commercial market or developed the application for the Library. | Text | This value is obtained from the APM Data Collection & Validation WorkSheet that is completed prior to an application being put into production. | Various; field will be blank if Application Type = In-House | Annual - field is not expected to change after the initial data entry. | APM Data Sheet (Intranet Form) | |
| App ID | ||||||||||||||||||
| Application Name | ||||||||||||||||||
| SSL Used | No | |||||||||||||||||
| Authentication | ||||||||||||||||||
| Application Interfaces | Interface 1 | Application Name | ||||||||||||||||
| Hosted Location | ||||||||||||||||||
| Hosting Vendor | Leave this field BLANK | |||||||||||||||||
| Data Flow | ||||||||||||||||||
| Purpose of Interface | ||||||||||||||||||
| Interface 2 | Application Name | |||||||||||||||||
| Hosted Location | ||||||||||||||||||
| Hosting Vendor | Leave this field BLANK | |||||||||||||||||
| Data Flow | ||||||||||||||||||
| Purpose of Interface | ||||||||||||||||||
| Interface 3 | Application Name | |||||||||||||||||
| Hosted Location | ||||||||||||||||||
| Hosting Vendor | Leave this field BLANK | |||||||||||||||||
| Data Flow | ||||||||||||||||||
| Purpose of Interface | ||||||||||||||||||
| Interface 4 | Application Name | |||||||||||||||||
| Hosted Location | ||||||||||||||||||
| Hosting Vendor | Leave this field BLANK | |||||||||||||||||
| Data Flow | ||||||||||||||||||
| Purpose of Interface | ||||||||||||||||||
| Interface 5 | Application Name | |||||||||||||||||
| Hosted Location | ||||||||||||||||||
| Hosting Vendor | Leave this field BLANK | |||||||||||||||||
| Data Flow | ||||||||||||||||||
| Purpose of Interface | ||||||||||||||||||
| Supporting Infrastructure | Application Server Hardware/Software | Server Name | ||||||||||||||||
| OS | ||||||||||||||||||
| OS Version | ||||||||||||||||||
| Vendor & Model | ||||||||||||||||||
| End of Life Date | ||||||||||||||||||
| Database Server Hardware/Software | Server Name | |||||||||||||||||
| OS | ||||||||||||||||||
| OS Version | ||||||||||||||||||
| Vendor & Model | ||||||||||||||||||
| End of Life Date | ||||||||||||||||||
| Web Server Hardware/Software | Server Name | |||||||||||||||||
| OS | ||||||||||||||||||
| OS Version | ||||||||||||||||||
| Vendor & Model | ||||||||||||||||||
| End of Life Date | ||||||||||||||||||
| Web Server (WS) Software | ||||||||||||||||||
| WS Version | ||||||||||||||||||
| Major Component | Component Description | |||||||||||||||||
| Server Name | ||||||||||||||||||
| OS | ||||||||||||||||||
| OS Version | ||||||||||||||||||
| Vendor & Model | ||||||||||||||||||
| End of Life Date | ||||||||||||||||||
| Certificates | Common Name | |||||||||||||||||
| Expiration Date |
no reviews yet
Please Login to review.
