Editorial Policy & Disclaimers
Welcome to The Identity Perimeter. This page outlines our editorial principles, conflict-of-interest safeguards, vendor neutrality standards, and legal disclaimers.
1. Non-Affiliation & Personal Views
All opinions, architectural designs, technical evaluations, and articles published on this website are strictly personal and represent solely the views of the author (Arvind Jha).
- No Employer Representation: The content published here is produced independently in a personal capacity. It does not represent, reflect, or constitute the strategies, opinions, architectural standards, or official endorsements of my current or past employers, clients, or affiliated organizations.
- No Confidential or Proprietary Information: Content is developed exclusively from public domain sources, open Request for Comments (RFCs), published specifications, and generic industry best practices. No internal, proprietary, unreleased, or confidential information from any employer is ever used or disclosed.
- Independent Time & Infrastructure: All research, drafting, coding, and hosting of this publication are conducted on personal equipment outside of standard professional working hours.
2. Editorial Independence & Conflict of Interest
As an active practitioner with experience spanning Network Engineering, Perimeter Security Architecture, and IAM Operations and Policy/Process Design, the following guidelines ensure strict editorial independence:
A. Focus on Open Standards & First Principles
Articles and book chapters prioritize open, vendor-neutral protocols and standards over proprietary lock-in architectures. Core subjects include:
- Protocols: OAuth 2.0 / 2.1, OpenID Connect (OIDC), SAML 2.0, SCIM 2.0, SPIFFE / SPIRE, FIDO2 / WebAuthn, Decentralized Identifiers (DIDs), and Verifiable Credentials (VCs).
- Architecture Paradigms: Zero Trust Architecture (NIST SP 800-207), Relationship-Based Access Control (ReBAC / Google Zanzibar), Attribute-Based Access Control (ABAC), and Non-Human Identity (NHI) Governance.
B. Standardized Vendor Evaluations
When commercial identity providers (IdPs), Privileged Access Management (PAM) tools, or cloud IAM suites are referenced or compared:
- Evaluations are based strictly on publicly available documentation, standard API specifications, and conformance to open RFCs.
- No commercial entity receives preferential placement, promotional copy, or unhedged endorsements.
- If an article analyzes a category where the author's employer or direct competitors operate, an explicit Disclosure Callout is included on that specific post.
3. Standard Disclosure Callout
Articles referencing commercial products or market comparisons include the following standard disclosure:
The author is an active practitioner in the enterprise IAM industry. This article is written from publicly available technical documentation and open standards specifications, representing solely personal technical analysis without employer sponsorship or commercial endorsement.
4. Dual Licensing & Usage Terms
To encourage open research and community sharing while protecting integrity:
- Written Content: Licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).
- Software & Simulators: Licensed under the MIT License.
See the full License & Terms page for attribution guidelines.
5. Corrections & Technical Errata
We strive for technical precision. If you identify an error, an outdated RFC reference, or an inaccurate protocol description, please open an issue or pull request on GitHub.