Details

Details include key deliverables, the cross-referenced and related enablers.

E0. Consult-free introduction to TechnologyMilestones

Description: this enabler is a free session to explore the functionality of TechnologyMilestones.

Related Enablers (often included):

none

E1. Build-IT Acquisition Strategy

Description: building IT acquisition strategy is the first step to gaining control over your information technology expenditures. Many technologies that have emerged over the past several years, when implemented properly, can save an organization cost, staff, and provide an enhanced level of cybersecurity. Creating an IT acquisition plan includes a careful review of all variables that impact information technology. Listed below are common enablers associated with developing an IT acquisition strategy.

Related enablers (often included):
E2. Consult-compute technologies
E4. Build-analytic strategy
E7. Build-infrastructure strategy
E10. Build-virtualization and container strategy
E13. Build-cloud strategy
E15. Build-inventory strategy
E18. Build-network strategy
E21. Build-data strategy
E24. Build-recovery and availability strategy
E50. Implement-technical writing
E51. Implement-technical visualization
E53. Implement-industry interest analysis
E56. Implement-roadmap development based on industry
E59. Build-patch management strategy
E61. Build-online services strategy
E64. Desktop modernization strategy

E2. Consult-Compute Technologies

Description: The evolution of the computer continues to enhance performance and enable organizations to maximize their investment in technologies that use compute components. Computer technologies are found in multiple components that exist within our environments, to include servers, storage, network gear, cybersecurity hardware, desktops, laptops, and IoT devices. Technologies found within these components include cores, sockets, RAM, CPU, GPU, and APUs. The application of computing technology should be focused on the organization's objective. For example, I am interested in purchasing analytics functionality; do I select servers with GPU's? How will my performance be impacted? How does buying different types of technologies increase my functionality and decrease my cost? During this Consulting session, we will discuss a logical approach to evaluating all compute base technologies, enabling your organization to make more informed decisions.

Related enablers (often included):
E1. Build-IT acquisition strategy
E4. Build-analytic strategy
E6. Consult-infrastructure strategy
E7. Build-infrastructure strategy
E9. Consult-virtualization and container technologies
E10. Build-virtualization and container strategy
E12. Consult-cloud strategy
E13. Build-cloud strategy
E17. Consult-network strategy
E18. Build-network strategy
E20. Consult-data strategy
E21. Build-data strategy
E47. Consult-aggregators in SIEMS

E3. Consult-Analytics, IoT and AI working together

Description: At the conclusion of the E3 Consulting session, the E4 enabler will assist in the building of the strategy. The world of data Analytics is upon us and will continue. Our ability to process and gain usable information from data collected continues to be a challenge for most organizations. The discussion really starts with the type of data, structured or unstructured, where that data will be processed, and the performance and security of the information collected. Actuators and sensors are adding additional data points that become challenging for many organizations. Does the mechanical pump in the air-conditioning system have a direct impact on customer satisfaction or margin? How does artificial intelligence assist individuals and organizations with the understanding of large sets of data? Embracing a strategy with a clear understanding of many of the impactful variables will allow organizations to enhance their investments.

E4. Build-Analytics Strategy

Description: The E4 enabler will assist in the building of strategy in preparation for the implementation of the strategy found within the E5 enabler. Building an analytic strategy for an organization is vitally important if the organization is looking to maximize the value of data collected within the environment. The strategy includes understanding the organizations infrastructure to include the hardware, software and process to establish the most efficient path and configuration for analytics. The infrastructure and data strategy within the environment will be a critical component of success for analytics, as well as the proper compute resources available to handle the often resource bound analytic services. A close companion to data analytics is the use of artificial intelligence to make decisions based upon specific variables or indicators within the environment. This level of automation, often called rules, provides the organization with consistent output and evaluation for adjustments to the analytic strategy. In analytic strategy cannot be absent of the impact of sensors, often associated with the Internet of things (IOT), and the value of the data collected. IOT actuators are often the recipient of data analytics and artificial intelligence activities. This enabler is designing the architecture and requirements for the implementation of the analytic environment.

Related Enablers (often included):

E2. Consult-compute technologies

E3. Consult-analytics, IOT and AI

E5. Implement-analytics strategy

E6. Consult-infrastructure strategy

E7. Build-infrastructure strategy

E8. Implement-infrastructure strategy

E17. Consult-network strategy

E18. Build-network strategy

E20. Consult-data strategy

E21. Build-data strategy

E5. Implement-Analytic Strategy

Description: The E5 enabler will assist in the implementation of the strategy defined by the organization or the E4 enabler. The implementation and fine-tuning of the environment will have a direct impact on cost, performance and viability of the data produced for the organization.

Related Enablers (often included):

E1. Build-IT Acquisition Strategy

E2. Consult-Compute Technologies

E3. Consult-Analytics, IoT and AI working together

E4. Build-Analytics Strategy

E5. Implement-Analytic Strategy

E6. Consult-Infrastructure Strategy

E7. Build-Infrastructure Strategy

E8. Implement-Infrastructure Strategy

E17. Consult-Network Strategy

E18. Build-Network Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E6. Consult-Infrastructure Strategy

Description: At the conclusion of the E6 Consulting session, the E7 enabler will assist in the building of the infrastructure strategy. The infrastructure includes all aspects of the information technology environment to include hardware, software, and process. Infrastructure historically is associated with “local” information technology resources, although must also include the discussion around the integration of cloud, in most cases in a hybrid model between local infrastructure and cloud infrastructure. This Consulting session will provide a brief introduction to many of the core tenants of an infrastructure and answer questions.

Related Enablers (often included):

E2. Consult-Compute Technologies

E7. Build-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E15. Build-IT Inventory Strategy

E18. Build-Network Strategy

E21. Build-Data Strategy

E24. Build-Recovery/availability Strategy

E7. Build-Infrastructure Strategy

Description: The E7 enabler will assist in the building of the infrastructure strategy to prepare for the implementation in the E8 enabler. The infrastructure includes all aspects of the information technology environment to include hardware, software, and process. Infrastructure historically is associated with “local” information technology resources, although must also include the discussion around the integration of cloud, in most cases in a hybrid model between local infrastructure and cloud infrastructure. This Consulting session will provide a brief introduction to many of the core tenants of an infrastructure and answer questions.

Related Enablers (often included):

E2. Consult-Compute Technologies

E6. Consult-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E15. Build-IT Inventory Strategy

E18. Build-Network Strategy

E21. Build-Data Strategy

E24. Build-Recovery/availability Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E57. Implement-Roadmap Development based on Industry

E60. Build-Patch Management Strategy

E8. Implement-Infrastructure Strategy

Description: The E8 enabler will assist in the implementation of the infrastructure strategy defined by the organization or the E7 enabler. The infrastructure includes all aspects of the information technology environment to include hardware, software, and process. Infrastructure historically is associated with “local” information technology resources, although must also include the discussion around the integration of cloud, in most cases in a hybrid model between local infrastructure and cloud infrastructure. This Consulting session will provide a brief introduction to many of the core tenants of an infrastructure and answer questions.

Related Enablers (often included):

E2. Consult-Compute Technologies

E6. Consult-Infrastructure Strategy

E7. Build-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E15. Build-IT Inventory Strategy

E18. Build-Network Strategy

E21. Build-Data Strategy

E24. Build-Recovery/availability Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E9. Consult-Virtualization and Container Technologies

Description: At the conclusion of the E9 Consulting session, the E10 enabler will be instrumental with building the strategy. In the session will talk about the differences between the hypervisor and containers and their applicability within our environments. Virtualization and container technology are a means to an end, although without the introduction of automation, the environments can become very difficult to manage. Consumers seek virtualization and containers often to drive down cost, which is a wonderful objective, although in this Consulting session we will discuss the reality of reduced cost and explore additional benefits to each of these key technologies found within our environment. For some, this Consulting session may include an evaluation of their current virtualization environment and their movement to containers.

Related Enablers (often included):

E2. Consult-Compute Technologies

E6. Consult-Infrastructure Strategy

E7. Build-Infrastructure Strategy

E8. Implement-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E11. Implement-Virtualization and Container Strategy

E12. Consult-Cloud Strategy

E13. Build-Cloud Strategy

E14. Implement-Cloud Strategy

E17. Consult-Network Strategy

E18. Build-Network Strategy

E19. Implement-Network Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E23. Consult-Recovery/availability Strategy

E10. Build-Virtualization and Container Strategy

Description: The E10 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E11 enabler. Building a virtualization and container strategy requires a clear understanding of the environment, the skill level of the individuals managing the environment, and the business objectives that have been associated with the introduction of virtualization and containers. The strategy will map out and make suggestions based upon the actual environment, which will include interviews and data collection. At the conclusion of E10, customers will have a clear strategy with functional requirements to begin modification of an existing environment or acquisition of new technologies. In addition, a phased in/roadmap approach will be presented within the strategy.

Related Enablers (often included):

E2. Consult-Compute Technologies

E6. Consult-Infrastructure Strategy

E7. Build-Infrastructure Strategy

E8. Implement-Infrastructure Strategy

E9. Consult-Virtualization and Container Technologies

E11. Implement-Virtualization and Container Strategy

E12. Consult-Cloud Strategy

E13. Build-Cloud Strategy

E14. Implement-Cloud Strategy

E17. Consult-Network Strategy

E18. Build-Network Strategy

E19. Implement-Network Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E23. Consult-Recovery/availability Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E57. Implement-Roadmap Development based on Industry

E11. Implement-Virtualization and Container Strategy

Description: The E11 enabler will be instrumental with the implementation of the strategy defined by the organization or the E10 enabler. If the organization currently has a virtualization and container strategy, the strategy will be reviewed and implemented. Our expertise extends to the primary virtualization technologies to include Microsoft, VMware, Red Hat and Open Stack (which is a KVM hypervisor very similar to Red Hat) and multiple container technologies and automation to include Docker and Kubernetes. Our implementation also includes the customization of policies to manage the automation required within either of these environments to maximize customers functionality with the technologies.

Related Enablers (often included):

E2. Consult-Compute Technologies

E6. Consult-Infrastructure Strategy

E7. Build-Infrastructure Strategy

E8. Implement-Infrastructure Strategy

E9. Consult-Virtualization and Container Technologies

E10. Build-Virtualization and Container Strategy

E12. Consult-Cloud Strategy

E13. Build-Cloud Strategy

E14. Implement-Cloud Strategy

E17. Consult-Network Strategy

E18. Build-Network Strategy

E19. Implement-Network Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E23. Consult-Recovery/availability Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E12. Consult-Cloud Strategy

Description: At the conclusion of the E12 Consulting session, the E13 enabler will be instrumental with building the strategy. Cloud Consulting session will a business and technical perspective, very dependent upon the recipient’s interest. Cloud strategy will explore multiple technologies to include “private” clouds either hosted at a commercial data center or within the organization’s firewall, “public” cloud technologies, hybrid cloud technologies which includes composable/converged technologies and the integration and coexistence between all the cloud-oriented technologies. It is important to note that cloud technology is not a new technology, it is simply a different delivery of technology. The Consulting session will include the details that are often glossed over when moving to cloud technologies.

Related Enablers (often included):

E2. Consult-Compute Technologies

E9. Consult-Virtualization and Container Technologies

E10. Build-Virtualization and Container Strategy

E11. Implement-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E14. Implement-Cloud Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E60. Build-Patch Management Strategy

E13. Build-Cloud Strategy

Description: The E13 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E14 enabler. Cloud strategy will include the items mentioned within the E12 enabler. The building of a cloud strategy includes an analysis that extends throughout the entire information technology environment. Questions related to performance, latency, data storage and the frequency at which the cloud environment will be utilized are all important variables to understand cost, risk and functionality for the organization. The E13 enabler will focus on the enterprise cloud strategy which may differ or complement the cloud strategy represented by the E61 and E62 enablers, focused at desktop/office automation usage.

Related Enablers (often included):

E2. Consult-Compute Technologies

E9. Consult-Virtualization and Container Technologies

E10. Build-Virtualization and Container Strategy

E11. Implement-Virtualization and Container Strategy

E12. Consult-Cloud Strategy

E14. Implement-Cloud Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E57. Implement-Roadmap Development based on Industry

E60. Build-Patch Management Strategy

E61. Consult-Online Services Strategy

E14. Implement-Cloud Strategy

Description: The E14 enabler will be instrumental with the implementation of the strategy defined by the organization or the E13 enabler. The implementation of the cloud strategy for the organization will include migration of data, availability of information during the migration process, and a project plan authored by years of experience implementing cloud strategies.

Related Enablers (often included):

E2. Consult-Compute Technologies

E9. Consult-Virtualization and Container Technologies

E10. Build-Virtualization and Container Strategy

E11. Implement-Virtualization and Container Strategy

E12. Consult-Cloud Strategy

E13. Build-Cloud Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E61. Consult-Online Services Strategy

E15. Build-IT Inventory Strategy

Description: The E15 enabler will build an information technology inventory strategy. Inventory collection and management is a key attribute of a secure environment, as it is difficult to create a secure environment without knowing where the technology assets are located. The strategy will assess and suggest modification (if required) to the current inventory collection process that includes hardware, software, servers, storage, networks, appliances and gaining importance IOT devices. The inventory strategy will include the strength of agent and agentless technologies, as well as the frequency of inventory updates in the presentation of the inventory collection, and a “test and validate” process to ensure the consistency and accuracy of your inventory.

Related Enablers (often included):

E16. Implement-IT Inventory collection and management

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E57. Implement-Roadmap Development based on Industry

E16. Implement-IT Inventory collection and management

Description: The E16 enabler will be instrumental with the implementation of the strategy defined by the organization or the E15 enabler.

Related Enablers (often included):

E15. Build-IT Inventory Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E17. Consult-Network Strategy

Description: At the conclusion of the E17 Consulting session, the E18 enabler will be instrumental with building the strategy. The Consulting session will include discussion related to network infrastructure design, to include routers, switches, web accelerators, hop management, firewalls, honeypot networks, IPS, IDS, DNS, transport/Internet/link layers, WAN optimizers, caching and other technologies of interest. The Consulting session is designed for both business and technologists. For the business consumer we will discuss the cost efficiency and savings associated with network technologies, vendor lock-in strategies that increase cost, introduce open standards like open flow to drive down cost for labor, hardware and maintenance contracts.

Related Enablers (often included):

E18. Build-Network Strategy

E19. Implement-Network Strategy

E23. Consult-Recovery/availability Strategy

E24. Build-Recovery/availability Strategy

E25. Implement-Recovery/availability Strategy

E26. Implement-Cyber Analysis

E29. Build-Contingency Plan

E32. Build-Cyber Security Controls

E18. Build-Network Strategy

Description: The E18 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E19 enabler. The strategy will include the optimization of your existing network infrastructure and a roadmap to drive out cost and increase efficiencies. The inclusion or exclusion of some technologies that may currently reside within your environment will have a direct impact on the cost related to network technologies. The strategy will explore the technologies introduced within the E17 enabler as well as others.

Related Enablers (often included):

E17. Consult-Network Strategy

E19. Implement-Network Strategy

E23. Consult-Recovery/availability Strategy

E24. Build-Recovery/availability Strategy

E25. Implement-Recovery/availability Strategy

E26. Implement-Cyber Analysis

E29. Build-Contingency Plan

E32. Build-Cyber Security Controls

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E57. Implement-Roadmap Development based on Industry

E19. Implement-Network Strategy

Description: The E19 enabler will be instrumental with the implementation of the strategy defined by the organization or the E18 enabler.

Related Enablers (often included):

E17. Consult-Network Strategy

E18. Build-Network Strategy

E23. Consult-Recovery/availability Strategy

E24. Build-Recovery/availability Strategy

E25. Implement-Recovery/availability Strategy

E26. Implement-Cyber Analysis

E29. Build-Contingency Plan

E32. Build-Cyber Security Controls

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E20. Consult-Data Strategy

Description: At the conclusion of the E20 Consulting session, the E21 enabler will be instrumental with building the strategy. Data strategy for an environment can be challenging as data continues to grow at unprecedented rates. The Consulting session will review strategies to manage the data explosion to include de-duplication, drive types to include NVMe to SSD to SATA, data file types to include file and object, archiving, NAS, SAN, DAS, local to cloud storage services, recoverability and availability of data, site to site replication at the storage layer or the operating system layer, HBA and HVA technologies and several others. From a business perspective the discussion will focus on utilization, cost per gigabyte, automated movement of workloads, commercial cloud versus local storage versus cloud hosted storage and other variables that have a direct impact on the functionality of the cloud service and cost-saving strategies.

Related Enablers (often included):

E12. Consult-Cloud Strategy

E13. Build-Cloud Strategy

E14. Implement-Cloud Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E23. Consult-Recovery/availability Strategy

E24. Build-Recovery/availability Strategy

E25. Implement-Recovery/availability Strategy

E30. Build-Risk Assessment Plan

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E21. Build-Data Strategy

Description: The E21 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E22 enabler. Data strategy for an environment can be challenging as data continues to grow at unprecedented rates. The strategy will include the ability to manage the data explosion to include de-duplication, drive types to include NVMe to SSD to SATA, data file types to include file and object, archiving, NAS, SAN, DAS, local to cloud storage services, recoverability and availability of data, site to site replication at the storage layer or the operating system layer, HBA and HVA technologies and several others.

Related Enablers (often included):

E12. Consult-Cloud Strategy

E13. Build-Cloud Strategy

E14. Implement-Cloud Strategy

E20. Consult-Data Strategy

E22. Implement-Data Strategy

E23. Consult-Recovery/availability Strategy

E24. Build-Recovery/availability Strategy

E25. Implement-Recovery/availability Strategy

E30. Build-Risk Assessment Plan

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E57. Implement-Roadmap Development based on Industry

E22. Implement-Data Strategy

Description: The E22 enabler will be instrumental with the implementation of the strategy defined by the organization or the E21 enabler.

Related Enablers (often included):

E12. Consult-Cloud Strategy

E13. Build-Cloud Strategy

E14. Implement-Cloud Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E23. Consult-Recovery/availability Strategy

E24. Build-Recovery/availability Strategy

E25. Implement-Recovery/availability Strategy

E30. Build-Risk Assessment Plan

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E23. Consult-Recovery/availability Strategy

Description: At the conclusion of the E23 Consulting session, the E24 enabler will be instrumental with building the strategy. The availability of information and services is critical to the functionality within an organization. The E23 Consulting session will discuss the many decisions that need to be made related to a recovery and availability strategy. We will start with discussing the services that currently exist within the environment and the need to classify the services and data as to their importance to the organization. For example, I have services (email, data sharing, web store) running within my organization. In the event of a failure, what services need to be restored within 30 minutes, four hours, 24 hours and how much data are you willing to lose? This level of questioning will assist you in designing an effective recovery and availability strategy for the organization. The reality is, not all services will be restored at the same time, and cost is directly associated with the level of service you are providing. We will discuss different types of synchronization technologies from the host level operating system to appliances and storage devices within the environment, and how latency can impact the difference between synchronous and asynchronous replication strategies. For some environments, the recovery and availability of services may be as simple as image capture and restoration.

Related Enablers (often included):

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E24. Build-Recovery/availability Strategy

E25. Implement-Recovery/availability Strategy

E28. Build-System Security Plan (SSP)

E29. Build-Contingency Plan

E30. Build-Risk Assessment Plan

E24. Build-Recovery/availability Strategy

Description: The E24 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E25 enabler. The strategy will look at all aspects of recoverability and availability built upon the priorities established by the organization. The strategy will review options and provide functional requirements to establish recoverability/availability of services and data within the organization, taking into consideration cost, security and the organizations priorities. E23 has additional details.

Related Enablers (often included):

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E23. Consult-Recovery/availability Strategy

E25. Implement-Recovery/availability Strategy

E28. Build-System Security Plan (SSP)

E29. Build-Contingency Plan

E30. Build-Risk Assessment Plan

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E57. Implement-Roadmap Development based on Industry

E25. Implement-Recovery/availability Strategy

Description: The E25 enabler will be instrumental with the implementation of the strategy defined by the organization or the E24 enabler.

Related Enablers (often included):

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E23. Consult-Recovery/availability Strategy

E24. Build-Recovery/availability Strategy

E28. Build-System Security Plan (SSP)

E29. Build-Contingency Plan

E30. Build-Risk Assessment Plan

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E26. Implement-Cyber Analysis

Description: The E26 enabler will be instrumental with the implementation of the strategy defined by the organization or the E27 enabler. With the ever-growing threat of a cyber-attack impacting an average of 15% -25% (up 3% from last year) of all organizations annually, with an average cost of recovery ranging from $250,000 to $4 million, organizations are paying closer attention to their cyber health. The implementation services within the E26 enabler will build many of the required security plans, review current log aggregation and event log management, examine the patch management strategy for the organization and perform other tasks that may include vulnerability and penetration scans. The analysis will also examine current event logs for known vulnerabilities and compare them with security policy objectives. This is an analysis and preparation enabler. Items may be discovered, for example hardening of a server, that can be added to the scope of work.

Related Enablers (often included):

E28. Build-System Security Plan (SSP)

E29. Build-Contingency Plan

E30. Build-Risk Assessment Plan

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E48. Consult-Aggregators and SIEMS

E49. Build-Event Log Strategy

E50. Implement-Event Log Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E60. Build-Patch Management Strategy

E27. Build-Cyber Policy

Description: The E27 enabler will be instrumental with the building of the strategy. Cyber policy is an overarching collection of rules and requirements to maintain cyber health throughout the environment. The building of a cyber policy includes user access policy, password policy, port policies, notification policies, QOS policy, system security plan, contingency plan, risk assessment plan, IT security policies, incident reporting, Internet vulnerabilities, employee and contractor exit policies, email encryption policy, email and Internet use policy, electronic acknowledgment policy, wireless policy, firewall policy, certification and accreditation guidelines and requirements, mobile device policy, breach policy, virtual server implementation policy, vulnerability assessment policy, protocol review policy and others is defined by the environment. The building of a cyber policy does not include the building of the security controls, which are the execution or enablement of the policy (see E31 to E33).

Related Enablers (often included):

E28. Build-System Security Plan (SSP)

E29. Build-Contingency Plan

E30. Build-Risk Assessment Plan

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E28. Build-System Security Plan (SSP)

Description: The E28 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E27 enabler. System security plans primarily focus on the strategy to protect and control information and services within an organization, serving as a benchmark of what right looks like. The implementation of a system security plan will vary dependent upon the organizations regulatory requirement or business vertical, although most system security plans are based on the United States Federal Government and SANS standards. Building a system security plan is grounded with the following common attributes: identify what systems within your environment require a system security plan and document how that system operates, identify the system owner the support staff and security staff so that there is a line of accountability, identify the administrative and business operations that are required and the staff to support those efforts. Once this information is been collected, the next step is to develop the controls required to support and provide accountability to the system security plan. At the conclusion of the work listed above, as well as other details not mentioned, a plan of remediation must be implemented. The system security plan establishes the baseline of what right looks like, the identification of staff and system artifacts are important, although without a plan of remediation when threat is discovered leaves you with very little cyber protection. The establishment of a system security plan is a document, the effectiveness of the plan is found in the development of the controls and accountability therein.

Related Enablers (often included):

E2. Consult-Compute Technologies

E4. Build-Analytics Strategy

E7. Build-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E15. Build-IT Inventory Strategy

E18. Build-Network Strategy

E21. Build-Data Strategy

E24. Build-Recovery/availability Strategy

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E60. Build-Patch Management Strategy

E62. Build-Online Services Strategy

E65. Build- Desktop Modernization Strategy

E29. Build-Contingency Plan

Description: The E29 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E27 and E28 enablers. Cyber contingency plan is designed to enable an organization to return to operational strength as soon as possible following a security breach. The cyber contingency plan includes steps to continue critical operations (see E23 and E24 - recoverability and availability strategy), contain the damage to digital assets to include personal and organization data. Once the situation is been contained and critical operations are functional, a restoration plan is initiated. The contingency plan includes data points from many of the other strategy documents.

Related Enablers (often included):

E2. Consult-Compute Technologies

E4. Build-Analytics Strategy

E7. Build-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E15. Build-IT Inventory Strategy

E18. Build-Network Strategy

E21. Build-Data Strategy

E24. Build-Recovery/availability Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E60. Build-Patch Management Strategy

E62. Build-Online Services Strategy

E65. Build- Desktop Modernization Strategy

E30. Build-Risk Assessment Plan

Description: The E30 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E27 and E28 enabler. With the ever-increasing dependency upon digital processing for organizations, a digital risk assessment plan or digital risk management plan is the next evolution in managing enterprise and security risk. The digital risk assessment plan clearly illustrates that digital risk to an organization is a business issue that is founded in technology, although is not just a technology issue. The enlightened definition and the implementation of a risk assessment plan for an organization assist in the transference or shared responsibility of digital risk between the “C suite” and information technology leaders. The risk assessment plan includes the management of digital risk across multiple lines of business to include information technology and security through the alignment of risk to business impact. Once the alignment of risk is been established, the risk assessment plan assists executives and organizations to understand the digital risk to their business and provide them with the strategy and decision points needed to balance the need to protect their organization with the need to run their organization. The objective of a risk assessment plan is to establish digital resiliency, detect digital threats and respond to minimize business impact and ultimately financial loss.

Related Enablers (often included):

E2. Consult-Compute Technologies

E4. Build-Analytics Strategy

E7. Build-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E15. Build-IT Inventory Strategy

E18. Build-Network Strategy

E21. Build-Data Strategy

E24. Build-Recovery/availability Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E60. Build-Patch Management Strategy

E62. Build-Online Services Strategy

E65. Build- Desktop Modernization Strategy

E31. Consult-Cyber Security Controls

Description: At the conclusion of the E31 Consulting session, the E32 enabler will be instrumental with building the strategy. Understanding the number of cyber security controls in the industry is likened to understanding tax law, few of us understand it or have the desire to understand. The Consulting session will assist customers in understanding the objectives of cyber security controls and expose them to strategies on establishing their cyber security strength. There are multiple established bodies of controls that are used as baselines, although the ultimate objective is to secure the environment. In order to secure the environment, the establishment of the security controls must start from the objective and move backward. In most environments, the implementation of security controls is built upon regulatory requirements, which can be a good first start, although unavoidably leaves gaps in the cyber security strategy. During this Consulting session we will discuss the value of understanding cyber objectives (data protection, insider threat, firewall standards) and assist you in finding the controls to meet your needs.

Related Enablers (often included):

E2. Consult-Compute Technologies

E4. Build-Analytics Strategy

E7. Build-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E15. Build-IT Inventory Strategy

E18. Build-Network Strategy

E21. Build-Data Strategy

E24. Build-Recovery/availability Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E60. Build-Patch Management Strategy

E62. Build-Online Services Strategy

E65. Build- Desktop Modernization Strategy

E32. Build-Cyber Security Controls

Description: The E32 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E33 enabler. Building cyber security control includes the control objective, description, control type and language to implement the control within the environment. Developing controls frequently aligned to regulatory requirements, although can be very customized and unique for the needs of the organization. E32 is a process of creating the controls, whereas E33 is the process of implementing those controls within the environment.

Related Enablers (often included):

E2. Consult-Compute Technologies

E4. Build-Analytics Strategy

E7. Build-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E15. Build-IT Inventory Strategy

E18. Build-Network Strategy

E21. Build-Data Strategy

E24. Build-Recovery/availability Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E60. Build-Patch Management Strategy

E62. Build-Online Services Strategy

E65. Build- Desktop Modernization Strategy

E33. Implement-Cyber Security Controls

Description: The E33 enabler will be instrumental with the implementation of the strategy defined by the organization or the E32 enabler. The implementation of cyber security controls requires what is frequently referred to as “hardening” of the system. The cyber security controls provide the instruction and objective, and the action associated with the security control is the implementation. It is not uncommon during the implementation to adjust multiple controls to make one control functional.

Related Enablers (often included):

E2. Consult-Compute Technologies

E4. Build-Analytics Strategy

E7. Build-Infrastructure Strategy

E10. Build-Virtualization and Container Strategy

E13. Build-Cloud Strategy

E15. Build-IT Inventory Strategy

E18. Build-Network Strategy

E21. Build-Data Strategy

E24. Build-Recovery/availability Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E60. Build-Patch Management Strategy

E62. Build-Online Services Strategy

E65. Build- Desktop Modernization Strategy

E34. Build-Inventory Management Strategy

Description: The E34 enabler will be instrumental with the building of the strategy. Building and inventory management strategy allows for the review of existing strategy or newly developed strategy to collect information about all electronic assets within the environment. Inventory management for information technology, typically addresses any component that uses a network protocol to communicate, frequently TCP/IP. The identification and strength of an inventory management strategy allows for the identification of rogue components on the network, which directly impact the security of the environment. Inventory management for most environments is lacking, although the inventory management strategy enabler is something all organizations should leverage to either check their existing solution or suggest new solutions.

Related Enablers (often included):

E16. Implement-IT Inventory collection and management

E35. Implement-Inventory Management

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E57. Implement-Roadmap Development based on Industry

E35. Implement-Inventory Management

Description: The E35 enabler will be instrumental with the implementation of the strategy defined by the organization or the E34 enabler. The implementation of an inventory management solution can be complex dependent upon the size of the organization. The implementation will follow the strategy, or a customer provided strategy.

Related Enablers (often included):

E15. Build-IT Inventory Strategy

E34. Build-Inventory Management Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E36. Consult-US Federal

Description: The E36 enabler will be instrumental with building a US Federal strategy for your organization. Understanding the US marketplace can be a challenge for individuals and organizations wishing to conduct business with the United States federal government. This Consulting session introduces and strengthens customers understanding of US federal business vertical. The Consulting session typically reviews everything from understanding the differences between the different types of federal agencies to contracting rules and regulations found with in the FAR. If your organization is developing solutions to be used with in the United States federal government, this Consulting session would be great for you to understand more about some of those things that you need to do when preparing to work for the US Government.

Related Enablers (often included):

E38. Build-DFARS Strategy

E39. Implement-DFARS

E40. Consult-508 Compliance

E41. Build-508 Compliance

E42. Implement-508 Compliance

E43. Consult-NIST Compliance

E44. Build-NIST Compliance

E45. Implement-NIST Compliance

E46. Implement-Policy to NIST compliance

E47. Build-hardware/software to NIST Strategy

E37. Consult-DFARS

Description: At the conclusion of the E37 Consulting session, the E38 enabler will be instrumental with building the strategy. DFARS is a security standard designed to assist the Department of Defense in maintaining a consistent cyber strength among partners, integrators and vendors that provide services and solutions to United States Department of Defense.

Related Enablers (often included):

E39. Implement-DFARS

E40. Consult-508 Compliance

E38. Build-DFARS Strategy

Description: The E38 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E39 enabler. Building a DFARS strategy requires an understanding of the customer’s environment to identify gaps that may need to be bridged or filled prior to performing as a DFARS approved vendor.

Related Enablers (often included):

E38. Build-DFARS Strategy

E40. Consult-508 Compliance

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E39. Implement-DFARS

Description: The E39 enabler will be instrumental with the implementation of the strategy defined by the organization or the E38 enabler.

Related Enablers (often included):

E38. Build-DFARS Strategy

E39. Implement-DFARS

E40. Consult-508 Compliance

Description: At the conclusion of the E40 Consulting session, the E41 enabler will be instrumental with building the strategy.

Related Enablers (often included):

E41. Build-508 Compliance

E42. Implement-508 Compliance

E41. Build-508 Compliance

Description: The E41 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E42 enabler.

Related Enablers (often included):

E40. Consult-508 Compliance

E42. Implement-508 Compliance

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E42. Implement-508 Compliance

Description: The E42 enabler will be instrumental with the implementation of the strategy defined by the organization or the E41 enabler.

Related Enablers (often included):

E40. Consult-508 Compliance

E41. Build-508 Compliance

E43. Consult-NIST Compliance

Description: At the conclusion of the E43 Consulting session, the E44 enabler will be instrumental with building the strategy.

Related Enablers (often included):

E44. Build-NIST Compliance

E45. Implement-NIST Compliance

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E44. Build-NIST Compliance

Description: The E44 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E45 enabler.

Related Enablers (often included):

E43. Consult-NIST Compliance

E45. Implement-NIST Compliance

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E45. Implement-NIST Compliance

Description: The E45 enabler will be instrumental with the implementation of the strategy defined by the organization or the E44 enabler.

Related Enablers (often included):

E43. Consult-NIST Compliance

E44. Build-NIST Compliance

E46. Implement-Policy to NIST compliance

Description: The E46 enabler will be instrumental with the analysis of your current policy to NIST controls and policies.

Related Enablers (often included):

E43. Consult-NIST Compliance

E44. Build-NIST Compliance

E45. Implement-NIST Compliance

E46. Implement-Policy to NIST compliance

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E47. Build-hardware/software to NIST Strategy

Description: The E47 enabler will assist the organization in understanding the NIST controls that are satisfied by the hardware / software. This is a value-add for customers.

Related Enablers (often included):

E43. Consult-NIST Compliance

E44. Build-NIST Compliance

E45. Implement-NIST Compliance

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E48. Consult-Aggregators and SIEMS

Description: At the conclusion of the E48 Consulting session, the E49 enabler will be instrumental with building the strategy.

Related Enablers (often included):

E26. Implement-Cyber Analysis

E27. Build-Cyber Policy

E31. Consult-Cyber Security Controls

E49. Build-Event Log Strategy

E50. Implement-Event Log Strategy

E49. Build-Event Log Strategy

Description: The E49 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E50 enabler.

Related Enablers (often included):

E26. Implement-Cyber Analysis

E27. Build-Cyber Policy

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E48. Consult-Aggregators and SIEMS

E50. Implement-Event Log Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E50. Implement-Event Log Strategy

Description: The E50 enabler will be instrumental with the implementation of the strategy defined by the organization or the E49 enabler.

Related Enablers (often included):

E26. Implement-Cyber Analysis

E27. Build-Cyber Policy

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E48. Consult-Aggregators and SIEMS

E49. Build-Event Log Strategy

E51. Implement-Technical Writing

Description: The E51 enabler provides technical writing for RFP, RFQ, RFI, Whitepapers, Blogs, Books and other material.

Related Enablers (often included):

E52. Implement-Technical Visualization

Description: The E52 enabler provides technical visualization for RFP, RFQ, RFI, Whitepapers, Blogs, Books, training videos and other material.

Related Enablers (often included):

E51. Implement-Technical Writing

E53. Consult-Industry Interest Analysis

Description: The E53 Consulting session reviews the industry focused interest analysis.

Related Enablers (often included):

E54. Implement-Industry Interest Analysis

Description: The E54 enabler will consume a defined set of information and produce a customized interest analysis.

Related Enablers (often included):

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E53. Consult-Industry Interest Analysis

E55. Implement-RFx Analysis and Alignment to Business

Description: Organizations process hundreds of requests for quote (RFP, RFQ, RFI) to discover opportunities. The process tends to be very manual and time-consuming for most organizations. The E55 enabler provides different levels with the intelligence to narrow down the hundreds of requests to the few that apply directly to the organization. If you’re looking to increase your opportunities and focus only on those that have a higher probability of when, this enabler is for you.

Related Enablers (often included):

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E54. Implement-Industry Interest Analysis

E56. Implement-RFx to Response Analysis

Description: The E56 enabler assist organizations with the analysis of a response to an RFP, RFQ, RFI. The process includes reviewing the RFP, RFQ, RFI request language and performing a comparison to the response language. This provides insight as to the effectiveness of the organization’s response and can directly impact the win ratio for the organization.

Related Enablers (often included):

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E57. Implement-Roadmap Development based on Industry

Description: Coupled with the E53 and E54 enablers, the E57 enabler will provide a roadmap of the industry demand with an organization’s current offerings and communications. The insight for the roadmap is typically extracted from strategic plans provided by large organizations, governments and countries. The mixture of these multiple strategic plans, representing customers throughout the globe, provides a very accurate visibility to purchasing habits. Organizations are bound to their strategic plans. If you’re wondering which direction your organization may want to take, this is a must-have enabler.

Related Enablers (often included):

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E53. Consult-Industry Interest Analysis

E54. Implement-Industry Interest Analysis

E58. Implement-Application Development

Description: The E58 assists organizations

Related Enablers (often included):

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E59. Implement-Cyber Compliance

Description: The E59 enabler will

Related Enablers (often included):

E28. Build-System Security Plan (SSP)

E29. Build-Contingency Plan

E30. Build-Risk Assessment Plan

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E48. Consult-Aggregators and SIEMS

E49. Build-Event Log Strategy

E50. Implement-Event Log Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E60. Build-Patch Management Strategy

Description: The E60 enabler will be instrumental with the building of the strategy in preparation for the implementation of your organizations strategy.

Related Enablers (often included):

E6. Consult-Infrastructure Strategy

E7. Build-Infrastructure Strategy

E8. Implement-Infrastructure Strategy

E9. Consult-Virtualization and Container Technologies

E10. Build-Virtualization and Container Strategy

E11. Implement-Virtualization and Container Strategy

E12. Consult-Cloud Strategy

E13. Build-Cloud Strategy

E14. Implement-Cloud Strategy

E17. Consult-Network Strategy

E18. Build-Network Strategy

E19. Implement-Network Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E26. Implement-Cyber Analysis

E28. Build-System Security Plan (SSP)

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E61. Consult-Online Services Strategy

Description: At the conclusion of the E61 Consulting session, the E62 enabler will be instrumental with building the strategy.

Related Enablers (often included):

E62. Build-Online Services Strategy

E63. Implement-Office 365 Strategy

E64. Consult-Desktop Modernization Strategy

E65. Build- Desktop Modernization Strategy

E66. Implement- Desktop Modernization Strategy

E62. Build-Online Services Strategy

Description: The E62 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E63 enabler.

Related Enablers (often included):

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E61. Consult-Online Services Strategy

E63. Implement-Office 365 Strategy

E64. Consult-Desktop Modernization Strategy

E65. Build- Desktop Modernization Strategy

E66. Implement- Desktop Modernization Strategy

E63. Implement-Office 365 Strategy

Description: The E63 enabler will be instrumental with the implementation of the strategy defined by the organization or the E62 enabler.

Related Enablers (often included):

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E61. Consult-Online Services Strategy

E62. Build-Online Services Strategy

E64. Consult-Desktop Modernization Strategy

E65. Build- Desktop Modernization Strategy

E66. Implement- Desktop Modernization Strategy

E64. Consult-Desktop Modernization Strategy

Description: At the conclusion of the E64 Consulting session, the E65 enabler will be instrumental with building the strategy.

Related Enablers (often included):

E65. Build- Desktop Modernization Strategy

E66. Implement- Desktop Modernization Strategy

E65. Build- Desktop Modernization Strategy

Description: The E65 enabler will be instrumental with the building of the strategy in preparation for the implementation of the strategy found within the E64 enabler.

Related Enablers (often included):

E50. Implement-Event Log Strategy

E51. Implement-Technical Writing

E64. Consult-Desktop Modernization Strategy

E66. Implement- Desktop Modernization Strategy

Description: The E66 enabler will be instrumental with the implementation of the strategy defined by the organization or the E65 enabler.

Related Enablers (often included):

E64. Consult-Desktop Modernization Strategy

E65. Build- Desktop Modernization Strategy

E67. Build- Subject Matter Expert (Infrastructure)

Description: The E67 enabler provides consulting efforts related to Infrastructure to include server, storage, network, cloud, IoT and supporting software and operating systems found within the infrastructure. Customers frequently select this enabler to assist with general CTO related tasks, assistance with RFP/RFQ/RFI response, etc..

Related Enablers (often included):

E1. Build-IT Acquisition Strategy

E2. Consult-Compute Technologies

E3. Consult-Analytics, IoT and AI working together

E6. Consult-Infrastructure Strategy

E9. Consult-Virtualization and Container Technologies

E12. Consult-Cloud Strategy

E17. Consult-Network Strategy

E20. Consult-Data Strategy

E23. Consult-Recovery/availability Strategy

E50. Implement-Event Log Strategy

E51. Implement-Technical Writing

E68. Build-Subject Matter Expert (Cyber)

E65. Build- Desktop Modernization Strategy

E68. Build- Subject Matter Expert (Cyber)

Description: The E68 enabler provides consulting efforts related to Cyber Security to include: analysis of a current state of readiness within an organization, scoping required for control and policy development, general consulting related to cyber concerns. Customers frequently select this enabler to assist with general CISO related tasks, assistance with RFP/RFQ/RFI response, etc.

Related Enablers (often included):

E26. Implement-Cyber Analysis

E27. Build-Cyber Policy

E28. Build-System Security Plan (SSP)

E29. Build-Contingency Plan

E30. Build-Risk Assessment Plan

E31. Consult-Cyber Security Controls

E36. Consult-US Federal

E37. Consult-DFARS

E40. Consult-508 Compliance

E43. Consult-NIST Compliance

E48. Consult-Aggregators and SIEMS

E50. Implement-Event Log Strategy

E51. Implement-Technical Writing

E67. Build-Subject Matter Expert (Infrastructure)

E69. Implement – Event Log Analysis

Description: The E69 enabler provides the analysis of log files related to defined system components against the established baseline or policy. The service reviews existing logs found within the system and compares discovered threats to existing controls and baselines. This provides customers with real time health assessment of controls. Very useful with compliance activities.

E70. Build – Report and Tasks

Description: The E70 enabler provides reporting an outline of tasks for the customer to complete. The reporting allows the customer to establish a current status, while providing for them the opportunity to complete the tasks with their current resources. TechnologyMilestones is available to assist with task execution as well.

E71. Build – Business aligned to Cyber

Description: The E71 enabler provides the analysis to align business need with cyber requirements, controls and baselines. Establishing the correct set of controls and baselines will allow organizations to fine-tune their cyber protection based on the business objective, as well allow the organization to prioritize remediation tasks based on business objectives and not simply cyber events.

E72. Build – System Priorities

Description: The E72 enabler reviews the organizations business objectives and prioritizes systems within the information technology environment. This alignment allows organizations to understand recovery times, availability of information, and potential loss of data. Breaking down the organization by business objectives and then aligning those objectives to the technology “systems” that support the business objectives will inadvertently save the organization cost and level set expectations throughout the organization. For example, many organizations use the same level of disaster recovery or high-availability for all aspects and technologies within their environment. This approach, although may appear to be simpler on the surface, can dramatically increase the cost of information technology. TechnologyMilestones takes an agnostic approach to system architecture and can provide a cost-effective approach to establishing and organizations “systems” in support of business outcomes.

E73. Implement – Inventory Collection

Description: The E73 enabler is the collection of information technology inventory for an organization performed by TechnologyMilestones staff. The output from this enabler/service is a CSV file that can be imported into any inventory collection system. TechnologyMilestones staff will also work with on-site inventory software used by the customer.

E74. Build – Technology Utilization

Description: The E74 enabler analyzes the current utilization of hardware and software resources within the organization and provide suggested cost savings. Understanding how storage is utilized, server processing resources are distributed, and network infrastructure is designed can have a direct impact on cost, availability and maintenance of an organization’s information technology environment. The E74 enabler/service produces a report of suggested actions that can be taken to drive down cost and increase efficiency.

E75. Implement – Internal PEN Testing

Description: The E75 enabler/service conducts vulnerability and penetration testing of your infrastructure from within your firewall. The output from the service provides the organization with a “to do” list to remediate discovered vulnerabilities.

E76. Implement – External PEN Testing

Description: The E76 enabler/service conducts vulnerability and penetration testing against your environment from external sources. The output from the service provides the organization with a “to do” list to remediate discovered vulnerabilities.

E77. Implement – Event Remediation

Description: The E77 enabler/service is used for event remediation related to discovered vulnerabilities or other services found within TechnologyMilestones. E77 may also include the installation and configuration of hardware and software within the environment as needed for remediation tasks.

E78. Build – Reduce IT Cost

Description: The E78 enabler/service is an analysis of IT cost, subscriptions, warranties and other associated cost and provides alternatives and potential cost reduction efforts.

E79. Build – Build Infrastructure Roadmap

Description: The E79 enabler/service build an information technology roadmap (1 to 3 years) based on existing assets and business objectives, aligned with current advancements in technology and infrastructure.

E80. Build – Build Analytics, IoT, Cyber Roadmap

Description: The E80 enabler/service is designed to build in analytic, IoT, cyber roadmap (1 to 3 years) based on existing assets and business objectives, aligned with current enhancements and emerging technologies.

E81. Build – Build Cloud Roadmap

Description: The E81 enabler/service is designed to build a cloud roadmap exploring local, hosted, hybrid and public cloud utilization models.

E82. Build – IT to Cloud Roadmap and Cost

Description: The E81 enabler/service is designed to build a roadmap for the migration from a local IT infrastructure to a cloud infrastructure. During the analysis, existing resources and assets will be analyzed for viability of moving to a cloud environment and balanced against current business objectives. The roadmap will include a phased in approach with thorough test plans and migration strategies.

E83. Build – Gap Analysis

Description: The E83 enabler/service will analyze current resources and assets, compared to a defined standard, and produce a gap list of customer tasks to become a compliant organization.

E84. Build – Cyber Policy Review

Description: The E84 enabler/service will analyze an organization’s current cyber policy, regardless of format, and provide a NIST control map to satisfy the cyber policies. This allows an organization to convert from their existing cyber policies into a NIST based framework.

E85. Build – Compliance Tasks

Description: The E85 produces a task list of compliance activities that are required for the environment to meet compliance regulations.

E86. Build – RFx to RFx Response Analysis

Description: The E86 creates a list of key phrases found within the RFx and compares the phrases to the response. This effort gives immediate insight as to the effectiveness of the response, and can increase win ratio considerably.

E87. Implement – Scan URLs

Description: Screen reading of information for compliance activities.

E88. Implement – Task List for Compliance

Description: Creation of tasks for customers that includes an export of a CSV and/or GANTT chart.

E89. Implement – Review customer Inventory

Description: Customer provides inventory that is reviewed by TM engineer.

E90. Implement – Service Alignment

Description: Align services to an organization’s outcomes.

E91. Implement – Purchase Components

Description: Acquisition of hardware, software, operating system, components needed for the organization.

E92. Implement – Install Components

Description: Installation of hardware, software, operating system, components needed for the organization.

LIST OF ALL ENABLERS

E0. Consult-free introduction to TechnologyMilestones

E1. Build-IT Acquisition Strategy

E2. Consult-Compute Technologies

E3. Consult-Analytics, IoT and AI working together

E4. Build-Analytics Strategy

E5. Implement-Analytic Strategy

E6. Consult-Infrastructure Strategy

E7. Build-Infrastructure Strategy

E8. Implement-Infrastructure Strategy

E9. Consult-Virtualization and Container Technologies

E 10. Build-Virtualization and Container Strategy

E11. Implement-Virtualization and Container Strategy

E12. Consult-Cloud Strategy

E13. Build-Cloud Strategy

E14. Implement-Cloud Strategy

E15. Build-IT Inventory Strategy

E16. Implement-IT Inventory collection and management

E17. Consult-Network Strategy

E18. Build-Network Strategy

E19. Implement-Network Strategy

E20. Consult-Data Strategy

E21. Build-Data Strategy

E22. Implement-Data Strategy

E23. Consult-Recovery/availability Strategy

E24. Build-Recovery/availability Strategy

E25. Implement-Recovery/availability Strategy

E26. Implement-Cyber Analysis

E27. Build-Cyber Policy

E28. Build-System Security Plan (SSP)

E29. Build-Contingency Plan

E30. Build-Risk Assessment Plan

E31. Consult-Cyber Security Controls

E32. Build-Cyber Security Controls

E33. Implement-Cyber Security Controls

E34. Build-Inventory Management Strategy

E35. Implement-Inventory Management

E36. Consult-US Federal

E37. Consult-DFARS

E38. Build-DFARS Strategy

E39. Implement-DFARS

E40. Consult-508 Compliance

E41. Build-508 Compliance

E42. Implement-508 Compliance

E43. Consult-NIST Compliance

E44. Build-NIST Compliance

E45. Implement-NIST Compliance

E46. Implement-Policy to NIST compliance

E47. Build-hardware/software to NIST Strategy

E48. Consult-Aggregators and SIEMS

E49. Build-Event Log Strategy

E50. Implement-Event Log Strategy

E51. Implement-Technical Writing

E52. Implement-Technical Visualization

E53. Consult-Industry Interest Analysis

E54. Implement-Industry Interest Analysis

E55. Implement-RFx Analysis and Alignment to Business

E56. Implement-RFx to Response Analysis

E57. Implement-Roadmap Development based on Industry

E58. Implement-Application Development

E59. Implement-Cyber Compliance

E60. Build-Patch Management Strategy

E61. Consult-Online Services Strategy

E62. Build-Online Services Strategy

E63. Implement-Office 365 Strategy

E64. Consult-Desktop Modernization Strategy

E65. Build- Desktop Modernization Strategy

E66. Implement- Desktop Modernization Strategy

E67. Build- Subject Matter Expert (Infrastructure)

E68. Build- Subject Matter Expert (Cyber)

E69. Implement – Event Log Analysis

E70. Build – Report and Tasks

E71. Build – Business aligned to Cyber

E72. Build – System Priorities

E73. Implement – Inventory Collection

E74. Build – Technology Utilization

E75. Implement – Internal PEN Testing

E76. Implement – External PEN Testing

E77. Implement – Event Remediation

E78. Build – Reduce IT Cost

E79. Build – Build Infrastructure Roadmap

E80. Build – Build Analytics, IoT, Cyber Roadmap

E81. Build – Build Cloud Roadmap

E82. Build – IT to Cloud Roadmap and Cost

E83. Build – Gap Analysis

E84. Build – Cyber Policy Review

E85. Build – Compliance Tasks

E86. Build – RFx to RFx Response Analysis

E87. Implement – Scan URLs

E88. Implement – Task List for Compliance

E89. Implement – Review customer Inventory

E90. Implement – Service Alignment

E91. Implement – Purchase Components

E92. Implement – Install Components