Peter Hyun grew up in Los Angeles as the son of Korean immigrants who arrived in the US in the mid-1970s on a one-way flight, chasing the American dream with more faith than certainty. His parents were born just before the Korean War and survived it as infants. Within a few years of arriving in the US, they had four sons in roughly three and a half years, including Peter and his twin, which meant there were years with three kids in diapers at the same time.

In Peter’s home, service was not a slogan. It was the family’s operating system. His father was a businessman who then became called to a pastoral ministry and then teaching theology. His mother was a nurse. His parents carried a deep reverence for their adopted country, and with that, a belief that government work  – “ministry” –  mattered because it was work done in service of others.

That reverence deepened through experience. As a kid, Peter traveled back to South Korea often, especially in the 1980s and 1990s. He remembers how different Seoul looked then, from (the lack of) basic infrastructure to everyday conveniences. Over time, he watched the country transform, and it left him with a lasting belief: government, when it works, helps people flourish.

Years later, Peter found his parents’ naturalization records at the home he grew up in. But the most personal moment came when he served as an Assistant U.S. Attorney in Alexandria, Virginia and participated in naturalization ceremonies. He would stand in a ceremonial courtroom, read the names of hundreds of new citizens, hand out small American flags, and move the court to administer the oath. Then he would tell the room something that was true and deeply personal: one generation earlier, his parents stood  for a similar ceremony in Los Angeles. Now their son was an officer of the United States, officially ushering others into citizenship. For him, it felt like a torch being passed.

That is the through line in Peter Hyun’s work today: reverence for service, paired with fluency in how government actually functions.

About The Series

This is the One Expert, One Topic series, where field experts select a topic and share essential insights using Matt Abrahams’ What / So What / Now What format. Presented in written form, it is meant to slow the thinking down, sharpen the takeaway, and give you clear next steps for where to learn more.

What

Peter Hyun,  who has served in all three branches of government and in state government, helps organizations navigate the intersection of technology, infrastructure, and government. Not just what a law says, but how it gets written, why it was written that way, how agencies implement it, how courts constrain it, and what that means for companies that still have to operate while the government debates, pauses, or changes direction.

He uses real examples. One is the Cybersecurity Information Sharing Act, a law designed (and co-authored by his former boss, the late Senator Dianne Feinstein) to encourage public-private collaboration around cyber threat information sharing by providing legal protections and clearer pathways for sharing. Peter has worked around this topic from multiple vantage points, including advising on what happens when statutory protections shift or lapse. His practical advice lives at the contract-and-process layer: re-review information-sharing agreements, tighten confidentiality and liability terms, document sharing decisions, and make sure governance is real, not implied.

In communications, he points to the evolution of the anti-abuse framework over the last few decades. The arc runs from the TCPA in 1991, to the Truth in Caller ID Act in 2010, to the TRACED Act in 2019, and then into implementation, including know your customer and know your upstream provider practices. His point is that communications regulation has been evolving quickly relative to industries like banking, where the roots of KYC stretch back decades. Businesses need to understand the context, not just the rule.

So What

Peter Hyun’s core argument is simple: many businesses are not fluent in how government works across its many bodies, and that lack of fluency is now a real risk.

Rules do not appear out of thin air, although sometimes it may seem like it. They come from a chain reaction. A lawmaker tries to solve a problem, a regulator turns that intent into enforceable rules, and courts decide whether the regulator stayed within its statutory and constitutional limits. If you only read the rule and ignore the chain, you get blindsided by the next step.

That shows up in very practical ways. A company can wake up to a congressional or regulator letter, a compliance shift, or a change in legal protections around cyber information sharing. The business cannot stop operating. Customers still need service. Threat actors do not wait. So the right posture is to see the play before it happens: what changed, what authority changed it, what liabilities now exist, what contracts and practices need to be updated, and what advocacy is required if the industry wants stability.

Now What

Peter Hyun’s advice is to build baseline fluency, then build muscle memory.

1. Learn the ecosystem, not just the headline rule. Know which statute you are operating under, what the agency believes it can do and is willing to do, and what courts have already said, and continue to say, about the boundaries.
   
2. Treat information sharing like a governed system, not a casual habit. Be proactive. Document decisions. Track what you share, with whom, and under what authority.
   
3. When legal protections shift or policy determinations take shape in new ways, re-review contracts and information-sharing agreements immediately and be proactive with engagement. Make sure permitted use, confidentiality, and liability language is not vague but purposeful.
   
4. If your industry depends on a framework, do not assume it will renew itself. Engage early. Advocate continuously.
   

Fluency is not about memorizing statutes. It is about understanding the machinery. And in a fast-moving regulatory environment, that understanding is the difference between reacting and anticipating.