In the high-stakes world of enterprise software, a "trust gap" often emerges between a vendor and its customers. It begins with a simple, common scenario: a product team launches an innovative feature, but a customer\u2019s security officer flags a discrepancy during an audit. Suddenly, the vendor is scrambling. Legal teams draft hurried responses, security experts perform retrospective architecture reviews, and compliance officers scramble to map the new feature against evolving frameworks like SOC 2, HIPAA, or the EU AI Act. <\/p>\n
For the customer, the experience is disjointed. They receive fragmented, often contradictory answers assembled under intense time pressure. The seams of the organization are exposed.<\/p>\n
New Relic, a leader in observability, decided that the industry-standard approach to these workflows\u2014siloed, sequential, and reactive\u2014was no longer sustainable. Their solution is STAR (System, Tooling, and Architecture Review)<\/strong>, a unified internal ecosystem designed to treat security, legal, compliance, privacy, and IT not as a series of hurdles, but as a single, cohesive discipline.<\/p>\n The genesis of STAR was not a desire for internal optimization, but a response to the shifting expectations of the enterprise customer. Modern regulatory landscapes are complex; customers are no longer asking if a vendor is "compliant." They are asking if a vendor treats security, legal, and privacy as a unified philosophy.<\/p>\n Historically, New Relic\u2014like most enterprise companies\u2014operated with departmental separation. Security owned the security queue, Legal owned the legal queue, and Compliance managed its own documentation. This "waterfall" approach to governance meant that if a compliance team flagged an issue late in the game, it could force a costly redesign of an architecture that security had already signed off on weeks prior.<\/p>\n New Relic recognized that this model was fundamentally broken. By moving to an integrated SLC (Security, Legal, and Compliance)<\/strong> review function, the company shifted from a "sign-off chain" to a collaborative team. <\/p>\n The transition followed a clear logic:<\/p>\n One of the most radical aspects of the STAR initiative is its refusal to adopt a standalone GRC platform. While GRC software is standard for most firms, these tools often create a "governance island"\u2014a place that engineers visit only when they have to, leading to friction and delayed compliance reporting.<\/p>\n New Relic chose to build STAR entirely within Jira. By embedding governance into the existing engineering toolchain, the company achieved a collapse of distance between the "gatekeepers" and the "builders."<\/p>\n Under the STAR model, every material change\u2014whether a new product feature, a third-party vendor integration, or a local software exception\u2014enters through a single portal. <\/p>\n The shift toward a unified review system has significant implications for how New Relic interacts with its customers. By treating governance as a unified discipline internally, the company can provide faster, more transparent, and more cohesive answers to customer inquiries.<\/p>\n The true test of any governance system is its ability to handle volatility. As AI adoption accelerates, regulatory frameworks like the EU AI Act and evolving state privacy laws are changing the game. Traditional, siloed review functions struggle to keep pace because these new requirements don’t respect departmental boundaries.<\/p>\n For example, a request involving generative AI touches upon legal (copyright and contract law), security (prompt injection and data leakage), and compliance (data privacy). Under the old model, these might have been treated as three separate, potentially conflicting reviews. Under STAR, they are viewed as a single, multidimensional problem. <\/p>\n Beyond the operational efficiency, the STAR system has fundamentally altered the culture at New Relic. Because review teams are now embedded in the engineering workflow, they are present at the beginning of the design phase. They move from being "blockers" who approve or reject at the finish line to "consultants" who help shape the architecture to be compliant by design. This early intervention significantly reduces the cost of course correction and fosters a culture of shared accountability.<\/p>\n Joseph Jang, legal counsel at New Relic, emphasizes that the goal of this system is to meet teams where they are. By focusing on the engineering architecture and the specific product capabilities, the legal and compliance functions become proactive partners in innovation rather than just auditors of it.<\/p>\n "The SLC review team sees it together in the same Jira record," notes the internal team. "When a question in the compliance lane has implications for the security assessment, the two reviewers are in the same conversation. This isn’t just about efficiency; it’s about building a foundation of trust that can scale as fast as the technology does."<\/p>\n The customer-facing benefits of this internal re-engineering are measurable. When a customer’s security officer asks a complex question about data handling or architectural integrity, New Relic’s Customer Trust team does not have to hunt for answers across five different departments. They leverage the collective STAR data to provide a comprehensive, unified response.<\/p>\n The effectiveness of this model is being validated by the increasing complexity of customer security questionnaires. As these questionnaires grow in length and specificity, the ability to synthesize information across security, legal, and compliance becomes a competitive advantage. <\/p>\n The STAR system serves as a case study for companies looking to bridge the gap between agility and governance. By rejecting the "waterfall" review process and embracing a "one intake, five disciplines" model, New Relic has demonstrated that governance does not have to be a drag on innovation.<\/p>\n As the industry moves toward a future where AI and cloud-native infrastructure require constant, real-time compliance, the "siloed" model of the past is effectively obsolete. New Relic\u2019s approach suggests that the companies that win in the next decade will be those that view trust, security, and compliance not as secondary functions, but as core components of their engineering DNA.<\/p>\n For New Relic, the journey of STAR is just beginning. As the remaining chapters of their series on this topic suggest, the framework is robust enough to handle everything from vendor procurement to the ethical complexities of artificial intelligence. One intake, five disciplines\u2014it is a simple, yet powerful, starting point for any organization striving for true, customer-centric trust.<\/p>\n","protected":false},"excerpt":{"rendered":" In the high-stakes world of enterprise software, a "trust gap" often emerges between a vendor and its customers. It begins with a simple, common scenario:…<\/p>\n","protected":false},"author":1,"featured_media":1654,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,1790,1791,1789,307,1788,4,20,3,675],"class_list":["post-1655","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-network-testing-and-monitoring","tag-diagnostic","tag-disciplines","tag-engineered","tag-five","tag-governance","tag-intake","tag-monitoring","tag-relic","tag-testing","tag-trust"],"_links":{"self":[{"href":"https:\/\/voicecabling.com\/index.php?rest_route=\/wp\/v2\/posts\/1655","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/voicecabling.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/voicecabling.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/voicecabling.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/voicecabling.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1655"}],"version-history":[{"count":0,"href":"https:\/\/voicecabling.com\/index.php?rest_route=\/wp\/v2\/posts\/1655\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/voicecabling.com\/index.php?rest_route=\/wp\/v2\/media\/1654"}],"wp:attachment":[{"href":"https:\/\/voicecabling.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1655"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/voicecabling.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1655"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/voicecabling.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1655"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}The Architecture of Trust: A Chronology of Change<\/h2>\n
From Silos to Systems<\/h3>\n
\n
The Design Philosophy: Why STAR Lives in Jira<\/h2>\n
The "One Door" Advantage<\/h3>\n
\n
Implications: Building for a Regulatory Future<\/h2>\n
Meeting the AI Challenge<\/h3>\n
Cultural Transformation<\/h3>\n
Official Perspectives on the New Model<\/h2>\n
Supporting Data and The Customer Experience<\/h2>\n
Conclusion: A Blueprint for Enterprise Governance<\/h2>\n