보안 결함을 수정하기 위해 AI를 사용할 때 신뢰하지만 검증

작성자

카테고리:

← 피드로
DEV Community · Iain Thomson · 2026-07-01 개발(SW)
Cover image for Trust but verify when using AI for fixing security flaws

Daily Context profile image Iain Thomson

AI Engineer World’s Fair Coverage

AI might seem like a magic bullet for fixing security issues, but it’s not that simple, warned Eugene Yan, a member of technical staff at Anthropic, during the newly inaugurated security track at AI Engineer World’s Fair. The effectiveness of AI in finding and fixing flaws is doubling every five months, he said, pointing to Mozilla releasing a 423-patch bundle in April. This was more patches than were released in all of 2025.

But while agents are good at finding and fixing flaws, the human element is still needed, say many security professionals. This is both to check that the AI has done the work properly and to make sure that seemingly low-risk bugs can’t be strung together to make a serious exploit that AI might not spot.

To fix this, Yan proposed a six-stage program. “We found that most teams converge in approximately these six steps, and a big chunk of my thoughts will be about these,” he told the crowd.

First, a threat-finding stage identifies a potential flaw and transfers it to phase two, a sandbox, to see if proof-of-concept code can exploit the issue. The third stage is a discovery phase in which the sample is checked against past issues that may have been fixed.

Stage four is an independent verification, which is designed to further filter out false positive results, and then the results are triaged to avoid flooding out human checkers. Then a patch is developed, and the code is kicked back to the discovery engine.

The end result, he argued, will be much more secure code that still maintains human oversight — while making the lives of security staff a lot easier. Of course, as AI systems improve further, that may not be the case forever if the current rate of engine improvements continues.

원문에서 계속 ↗

코멘트

답글 남기기

이메일 주소는 공개되지 않습니다. 필수 필드는 *로 표시됩니다