myself@terminal: ~/resumeread-only
EDWARDCHER(7)Professional ManualEDWARDCHER(7)
$ man 7 edwardcher

NAME

Edwardcher Monreal — Principal Solutions Architect at HID, trusted digital identity and cybersecurity practitioner, pragmatic programmer, and technology advisor.

INTRODUCTION

I build trust, bridge perspectives, and deliver solutions that work. For more than 25 years, I have moved between writing code, integrating systems, solving security problems, and helping organizations turn complex requirements into practical technology decisions.

Today, as Principal Solutions Architect at HID, I work at the intersection of digital identity, authentication, cybersecurity, and business outcomes. I remain an engineer at heart: curious about how things work, willing to test assumptions, and convinced that good architecture must survive contact with the real world.

This manual is my independent professional profile. It documents the skills, principles, and interests behind my work, while the rest of this site contains my experiments, writing, and personal perspectives.

SYNOPSIS

edwardcher [--architect] [--developer] [--security]
           [--identity] [--authentication] [--integration]
           [--advisor] [--speaker] [--terminal-first]

DESCRIPTION

My work is grounded in identifying and composing proven technologies into sustainable solutions with measurable outcomes. I prefer interoperability over lock-in, security that can be operated, and architectures that account for people, processes, and investment—not just technical elegance.

Based in Singapore, I work primarily across Asia-Pacific, with experience collaborating on international engagements. My career has included software development, systems integration, security consulting, technical project management, and customer-facing solution architecture. These perspectives help me translate between developers, security teams, executives, partners, and end users.

CURRENT ROLE

Principal Solutions Architect — HID
Trusted Digital Identity · Identity and Access Management · Authentication

  • Design and articulate identity and authentication architectures for enterprise, financial-services, and other security-sensitive environments.
  • Connect business requirements to integration patterns, assurance levels, threat models, deployment constraints, and operational ownership.
  • Work with customers and partners on phishing-resistant authentication, passkeys, smart cards, PKI, and risk-aware identity journeys.
  • Help reconcile usability, interoperability, lifecycle management, and security controls across physical and digital environments.

OPTIONS

ParameterCapability
--architectSolution architecture, system boundaries, design trade-offs, implementation strategy
--identityIAM, CIAM, identity lifecycle, workforce and customer identity, converged access
--authenticationFIDO2, WebAuthn, passkeys, MFA, OTP, phishing resistance
--cryptoPKI, PIV, certificates, smart cards, hardware-backed and device-bound credentials
--integrationOAuth 2.0, OIDC, SCIM, APIs, enterprise and banking integrations
--riskRisk-based authentication, fraud signals, threat modeling, assurance and controls
--developerPolyglot programming, test-driven-development, debugging, automation, prototyping, system integration
--advisorStakeholder alignment, security investment decisions, architecture communication
--speakerTechnical presentations, practitioner discussions, identity thought leadership
--terminal-firstUnix-style composition, terminal-based workflows, reproducible experiments, unrepentant emacs user

EXPERIENCE

25+ years across engineering, integration, security, and architecture. I have worked from implementation details to executive discussions, including environments in banking, telecommunications, enterprise, government, and other sectors with demanding trust requirements.

My professional journey has included:

  • Software engineering: Understanding systems by building, testing, and troubleshooting them.
  • Systems integration: Making independently designed components work together across real organizational boundaries.
  • Security practice: Treating identity, credentials, cryptography, and risk as connected architectural concerns.
  • Solution architecture: Turning competing technical and commercial priorities into implementable designs.
  • Technical engagement: Explaining complex subjects clearly, influencing decisions, and building trusted working relationships.

Detailed chronology, selected engagements, and measurable project outcomes can be added here later.

SELECTED TECHNICAL DOMAINS

Identity assurance and authentication: FIDO2/WebAuthn, device-bound passkeys, passwordless migration, credential provisioning and recovery, MFA, authentication journeys, and lifecycle governance.

Cryptographic trust: PKI, certificate-based authentication, PIV and smart cards, hardware-backed credentials, and converged physical-to-digital identity.

Platforms and integration: OIDC, OAuth 2.0, SCIM, directory services, cloud and on-premises architectures, identity-provider integrations, and API-driven workflows.

Risk and security: Threat modeling, phishing resistance, contextual and risk-based authentication, fraud prevention, auditability, and pragmatic controls.

SELECTED PUBLIC WORK

I write and speak about the changing identity perimeter, passwordless adoption, authentication resilience, and why trust should be anchored in verifiable credentials and devices.

PHILOSOPHY

Building Trust | Bridging Perspectives | Delivering Solutions That Work

Use proven technologies when they fit. Do not reinvent the wheel for novelty; when the wheel is broken—or square—be prepared to build a better one. Security must serve real users and real operations, not simply pass an architecture review.

I favor device-bound trust, standards-based integration, and securing the complete identity journey rather than only the login event. A successful solution balances assurance, interoperability, user experience, operational sustainability, and cost.

WORKING STYLE

--pragmatic Validate assumptions with working prototypes and field evidence.

--composable Prefer small, understandable tools and standards-based interfaces.

--terminal-first Use text, scripts, git, and repeatable commands wherever they improve clarity and control.

--collaborative Bridge engineering, security, product, and business perspectives.

--continuous-learning Stay curious, experiment, and revise conclusions when evidence changes.

BEYOND WORK

I remain a programmer and technology enthusiast at heart. I enjoy experimenting with technologies, building small practical projects, and exploring terminal-first workflows that keep things simple and efficient. Beyond technology, I love traveling with my family, researching practical gear that improves my everyday carry, and appreciating mechanical watches that reflect my interest in craftsmanship, engineering, and purposeful design.

This site goes beyond a corporate biography. It is my personal space to document discoveries, share lessons learned, explore ideas, and bring together my professional perspectives and personal interests.

SEE ALSO

NOTES

This is an independent personal website. Opinions expressed here are my own and do not necessarily represent HID. The manual is a living document; specific project outcomes, career milestones, and additional references will be refined over time.

EDWARDCHER(7)ENDq · return home