Book Image

ServiceNow for Architects and Project Leaders

By : Roy Justus, David Zhao
Book Image

ServiceNow for Architects and Project Leaders

By: Roy Justus, David Zhao

Overview of this book

ServiceNow is the leading enterprise service management platform that enables the effective management of services in a modern enterprise. In this book, you’ll learn how to avoid pitfalls that can challenge value realization, where to focus, how to balance tradeoffs, and how to get buy-in for complex decisions. You’ll understand the key drivers of value in ServiceNow implementation and how to structure your program for successful delivery. Moving ahead, you’ll get practical guidance on the methods and considerations in securely using ServiceNow. You’ll also learn how to set up a multi-instance environment including best practices, patterns and alternatives in the use and maintenance of a multi-instance pipeline. Later chapters cover methods and approaches to design processes that deliver optimal ROI. Further, you’ll receive tips for designing technical standards, designing for scale, ensuring maintainability, and building a supportable instance. Finally, you’ll focus on the innovative possibilities that can be unlocked in a ServiceNow journey which will help you to manage uncertainty and claim the value of being an early adopter. By the end of this book, you’ll be prepared to lead or support a ServiceNow implementation with confidence that you’re bringing not only a solution but also making an impact in your organization.
Table of Contents (17 chapters)
Part 1 – Pursuit of Value
Part 2 – The Checklist
Part 3 – From Success to Innovation

Planning for instance hardening

Knowing that you should be securing your instances but not knowing where to start is a tough place to be. Fortunately, with a few simple guidelines and tools provided by ServiceNow, you can make a big impact quickly. Let’s start with a clear picture of where security should be applied in your ServiceNow deployment.

Implementation security measures

With security often seen as a “checklist” activity that must be addressed prior to go-live, it can be tempting to try to focus the security standards for your environments on the production instance only, hardening it as your initial cutover approaches. Teams taking this approach often restrict the data that flows to sub-production instances and adopt less strenuous controls in those instances. Others allow security-related tasks to be undertaken in a final hardening cycle prior to production rather than continuously throughout the implementation. Rather than adopt these approaches...