Visualização de leitura

“채용이 곧 공격 경로”…AI 악용한 가짜 IT 인력, 기업 내부 위협으로 확산

최근 몇 년 사이 가짜 IT 인력을 채용하는 문제는 점점 심각해지고 있지만, 이를 공개적으로 인정하려는 기업은 많지 않다. 포춘 500 기업부터 중소 조직에 이르기까지 원격 채용 방식이 악용되면서, 실제 신원이 아닌 인물에게 신뢰 기반 접근 권한이 부여되는 사례가 발생하고 있으며 이는 내부자 위협으로 이어질 수 있다.

추정에 따르면 미국 전역에서 수천 명의 가짜 IT 인력이 활동 중이며, 이들은 정보와 지식재산(IP), 데이터 탈취는 물론 해외로의 업무 외주화, 시스템 교란, 외국 정부로의 자금 유입 등 다양한 위협 행위를 수행할 수 있는 위치에 있다.

미국 기업 아마존(Amazon)의 최고보안책임자(CSO) 스티브 슈미트는 “북한이 IT 직무를 확보하기 위해 시도한 1,800건 이상의 사례를 차단했으며, 그 수는 계속 증가하고 있다”고 밝혔다.

일부는 개인적인 이익을 위해 미국 직원으로 위장하고, 또 다른 경우에는 북한과 같은 국가 단위 조직이 자금 확보 및 기타 불법 목적을 위해 IT 인력으로 위장하기도 한다.

현재 AI 기술은 딥페이크 생성, 더욱 정교한 영상 면접 수행, 빠른 신원 변경 등을 가능하게 하며 이러한 위협을 한층 고도화하고 있다.

슈미트는 공격 방식 역시 변화하고 있다며, 단순히 프로필을 조작하는 수준을 넘어 실제 미국인의 신원을 구매해 활용하는 단계로 진화하고 있다고 경고했다.

사이버보안 기업 센티넬원(SentinelOne)의 위협 연구원 톰 헤겔은 “이 문제는 전통적인 의미의 채용 사기가 아니다”라며 “공격자가 ‘채용되는 것’을 첫 단계로 삼는 내부자 위험 문제”라고 설명했다.

CIO, CISO 등 IT 리더들은 가짜 및 사기성 IT 인력에 대해 지속적으로 경계해야 하지만, 조직이 이를 인지하지 못한 채 피해를 입는 경우도 적지 않다.

가짜 인력은 어떻게 채용을 통과하나

채용 과정에는 단일한 실패 지점이 존재하지 않는다. 가짜 및 사기성 IT 인력은 신원을 숨기고, 역량과 경력을 조작하며, 면접과 검증 절차를 별다른 의심 없이 통과한다.

센티넬원은 북한 연계 IT 인력 조직과 관련된 약 360개의 가짜 인물과 1,000건 이상의 채용 지원 사례를 추적했으며, 자사 채용에도 실제 지원 시도가 있었다고 밝혔다.

헤겔에 따르면 공격자들은 점점 더 대규모로 사회공학 기법과 신원 은폐 전략을 활용하고 있으며, 채용 과정은 이들이 침투하기 위한 핵심 진입 지점으로 작용하고 있다.

이들은 합성 또는 도용된 신원을 기반으로 이력서와 온라인 프로필을 만들고, 스크립트나 대리 응시자, AI 기반 응답을 활용해 면접을 통과한다. 또한 백그라운드 체크는 제출된 정보만 검증하기 때문에 이러한 조작을 그대로 통과시키는 구조다.

헤겔은 “가짜 구직자들은 이제 AI 도구를 활용해 실제 지원자를 모방하고 있다”라며 “초기 신원 검증을 통과할 수 있는 합성 신원을 만들고, 경력 이력을 조작하며, 실시간 AI 지원을 통해 면접에서도 설득력 있게 응답한다”고 설명했다.

보안 기업 플래시포인트(Flashpoint)의 조사에서는 HR 및 채용 플랫폼 계정 정보가 저장된 악성코드 감염 시스템, 번역된 면접 코칭 메모가 담긴 브라우저 기록, 해외에서 기업 장비를 원격 조작하는 ‘노트북 팜’, 그리고 가짜 경력 검증을 위한 페이퍼컴퍼니 등이 확인됐다.

문제는 채용 이후다. 채용이 완료되면 계정과 장비가 지급되고 시스템 접근 권한이 부여되면서 이들은 곧 내부 신뢰 인력으로 전환된다. 헤겔은 “장기적인 위험은 단순히 가짜 직원을 채용하는 데 그치지 않는다”라며 “기업 시스템과 민감한 데이터에 악의적인 접근을 스스로 열어주는 결과로 이어질 수 있다”고 경고했다.

가짜 IT 인력 대응 방법

CIO가 가짜 IT 인력을 의심하는 순간부터 문제의 성격은 단순 채용 이슈에서 내부자 리스크 관리로 전환된다. 이후 대응 절차가 무엇보다 중요해진다.

몽고DB(MongoDB) 재직 당시 조사 및 대응을 총괄했던 IANS 자문이자 베드록 데이터(Bedrock Data) CSO 조지 거초우는, 재직했던 회사가 북한 연계 가짜 IT 인력을 채용한 사실을 뒤늦게 인지하고 조사에 착수한 경험을 공유했다.

문제는 엔드포인트 보안 솔루션 제거 시도에서 시작됐다. 거초우는 “크라우드스트라이크 오버워치(CrowdStrike Overwatch)를 포함한 보안 기능을 제거하려는 시도가 감지됐고, 이후 해당 노트북이 북한 IP 주소와 통신하는 정황이 포착됐다”고 설명했다.

이어 “보안 도구 조작과 북한 연계 트래픽이 동시에 나타난 것은 일반적인 신규 입사자의 행동이 아니라는 명확한 신호였다”고 덧붙였다.

조사 결과 해당 인력은 도용된 신원에 AI로 생성된 이력서, 스크립트 기반 면접 답변을 결합해 검증 절차를 통과한 것으로 드러났다. 기존 백그라운드 체크는 제출된 정보만 확인할 뿐, 조작 여부를 탐지하지 못하는 한계가 있었다.

거초우는 “많은 검증 시스템이 조작된 경력, 합성 신원, 재활용된 개발자 프로필을 식별하지 못한다”라며 “이 때문에 별다른 경고 없이 채용과 면접을 통과할 수 있었다”고 설명했다.

이후 조사에서는 보안 도구 비활성화 시도, 장비 내 지속 접근 확보, 권한 상승 탐색 등의 행위가 확인됐다. 거초우는 “발각되지 않았다면 연방 보안 인증(FedRAMP) 환경까지 접근했을 가능성이 있다”며 위험성을 강조했다.

놓치기 쉬운 ‘경고 신호’…단편적 대응이 문제

사건 이후 돌아보니 여러 이상 징후가 있었다. 면접 영상 품질이 낮고 화면이 불명확했으며, 통화마다 억양이 일관되지 않았다. 면접 평가도 분산돼 있었고, 이를 통합 검토하는 체계가 없었다.

노트북 배송 주소를 마지막 순간 변경한 점도 주요 단서였다. 거초우는 “이는 ‘섀도우 워커’들이 자주 사용하는 전형적인 수법”이라고 말했다.

문제는 이러한 징후가 각각 개별적으로는 채용을 막을 정도로 치명적이지 않았다는 점이다. 거초우는 “각 이상 징후를 통합해 판단하는 역할이 없었기 때문에, 엔드포인트 경고가 발생하기 전까지 패턴을 인식하지 못했다”고 설명했다.

발견 이후 대응…즉각 차단과 전면 조사

가짜 인력이 확인되자 팀은 즉시 장비를 격리하고 모든 계정을 폐기했으며, 포렌식 조사를 실시하고 연방 당국에 신고했다. 조사 결과 데이터 유출이나 내부 확산은 발생하지 않은 것으로 확인됐다.

이후 대응 조치로는 채용 과정에서의 신원 검증 강화, 초기 이상 징후를 통합 관리하는 ‘옐로 플래그’ 담당자 지정, 신규 입사자에 대한 신뢰 확보 전까지 접근 권한 제한 등이 도입됐다.

“신원보다 행동”…채용 이후 모니터링 강화해야

거초우는 채용 이후 행동 기반 모니터링의 중요성도 강조했다. 단순 자격 증명보다 실제 사용 행태가 위장 인력을 식별하는 핵심이라는 설명이다.

이에 따라 기업은 보안 또는 HR 부서 내 검토 담당자를 지정해 면접 영상 품질 저하 등 채용 과정의 불일치를 식별해야 한다. 또한 AI로 생성된 링크드인 프로필, 이력서 불일치, 장비 배송 주소 변경 등도 주요 점검 대상이다.

패널 면접과 프로젝트 기반 평가를 통해 도용 또는 가짜 개발자 신원을 재활용하는 지원자를 식별하고, 신규 입사자에게는 초기 단계에서 민감 데이터나 운영 환경 접근을 제한하는 것이 필요하다.

또한 IAM, EDR, VPN 등 보안 에이전트가 비활성화될 경우 경고를 설정하고, 가짜 개발자 채용 상황을 가정한 탐지·대응 훈련도 병행해야 한다.

거초우는 “근무 시간 외 접근, 내부 시스템 전반에 대한 과도한 검색, 대량의 문서 및 코드 저장소 복제 시도 등도 주요 이상 징후로 주의 깊게 살펴야 한다”고 강조했다.

IT 리더들이 내부에서 목격하는 현실

고용 사기 문제는 앞으로 더욱 악화될 전망이다. 가트너는 2028년까지 전 세계 채용 지원자의 4명 중 1명이 가짜일 것으로 예측했다.

에너지솔루션(Energy Solutions)의 CIO 데이비드 웨이송은 “가짜 및 사기성 구직자의 증가는 조직 전반에 걸친 ‘전염병’ 수준으로 확산되고 있다”고 말했다.

웨이송에 따르면 공격자들은 데브옵스, 시스템 관리자, 데이터 엔지니어, 데이터베이스 관리자 등 높은 접근 권한을 가진 기술 직무를 집중적으로 노린다. 이러한 직무에 채용될 경우 핵심 시스템에 대한 깊은 가시성과 통제 권한을 확보할 수 있기 때문이다.

웨이송은 “이들 직무는 사실상 ‘성문 열쇠’를 쥔 역할”이라며 “시스템 접근을 노린다면 일반 개발자보다 훨씬 가치가 높은 목표”라고 설명했다.

규제가 엄격한 에너지 시장에서 운영되는 에너지솔루션은 미국 내 인력 채용과 데이터의 미국 내 보관이 계약상 의무화돼 있다.

웨이송은 가짜 IT 인력을 직접 식별한 경험을 바탕으로 다른 IT 리더들에게 경고를 전했다. 가장 초기 징후 중 하나는 비정상적인 지원자 급증이었다. 수 시간 만에 수백 건의 지원서가 몰렸으며, 이는 기업 인지도 대비 과도한 수준으로 자동화 또는 조직적인 활동을 시사했다.

면접 단계에서는 ‘신원 바꿔치기’ 사례도 확인됐다. 웨이송은 “전화 인터뷰를 통과한 사람과 화상 면접에 등장한 사람이 다르고, 이후 또 다른 인물이 나타나는 경우도 있었다. 모두 동일한 이름과 이력서를 사용했다”고 밝혔다.

문제의 근본 원인 중 하나는 기존 채용 절차가 정보와 역량을 개별적으로 검증한다는 점이다. 웨이송은 “전통적인 백그라운드 체크는 제출된 정보만 확인할 뿐, 사기를 식별하지 못한다”고 지적했다.

일부 CIO에게는 불편한 현실이지만, 이들이 수행하는 업무 결과 자체는 높은 수준일 수 있으며, 탐지는 성과가 아닌 이상 징후를 통해 이뤄지는 경우가 많다.

그러나 가짜 IT 인력은 보안 위험뿐 아니라 비즈니스와 규제 리스크도 동시에 초래한다. 특히 규제 산업에서는 계약 위반, 규제 조사, 고객 신뢰 상실로 이어질 수 있다.

웨이송은 “가짜 IT 인력은 보안 문제를 넘어 비즈니스와 컴플라이언스 측면에서도 심각한 위험을 초래하며, 규제 산업에서는 계약 위반과 규제 리스크, 고객 신뢰 훼손으로 이어질 수 있다”고 강조했다.

가짜 IT 인력 대응 전략

아마존(Amazon)은 AI 기반 도구와 인적 검토를 병행해 의심스러운 연락처 정보와 허위 학력, 가짜 기업 이력을 식별하고 있다. 또한 보안팀은 수상한 링크드인 프로필을 표시하고, 대면 면접과 사무실 출근을 강화하며, 컴퓨터 사용 패턴과 업무 품질을 모니터링하고 물리적 토큰 기반 인증을 적용하고 있다.

스티브 슈미트는 포츈 인터뷰를 통해 IT와 HR 부서 간 긴밀한 협력이 문제 해결의 핵심이라고 강조했다. 그는 “문제를 초기에 발견하는 것이 HR 조직 입장에서도 훨씬 비용 효율적”이라고 밝혔다.

센티넬원의 헤겔은 채용에 대한 접근 방식 자체를 바꿔야 한다고 지적했다. 그는 “채용을 단순 인사 절차가 아닌 접근 권한 통제 문제로 봐야 한다”라며 “신원을 한 번 확인하는 체크리스트로 끝내지 말고, 원격 채용을 특권 접근 권한 부여처럼 다뤄야 한다”고 설명했다.

에너지솔루션의 웨이송은 경험을 바탕으로 채용 시스템과 내부 프로세스 전반에 걸쳐 대대적인 변화를 도입했다.

채용 공고 단계부터 기술 직무 지원자가 요구사항과 책임을 명확히 이해하도록 모든 문서에 이를 명시했다. 웨이송은 “특히 ‘완전 원격 근무’라는 표현을 제거한 이후, 사기 시도와 해외 지원이 눈에 띄게 줄었다”고 말했다.

이어 “제로 트러스트 방식이 이상적이긴 하지만 채용 과정 자체를 저해하거나 정상 지원자를 위축시켜서는 안 된다”라며 “자동화된 사기 지원자가 애초에 채용 파이프라인에 들어오지 못하도록 충분한 대응책을 마련해야 한다”고 강조했다.

지원자 급증 문제를 해결하기 위해 에너지솔루션은 채용 공고에 강력한 CAPTCHA를 적용하고, 직원 추천 보너스를 통해 내부 네트워크 기반 채용을 확대했으며, 신규 입사자에게는 90일 성과 검증 기간을 운영하고 있다.

채용 심사 과정에서는 전화 대신 영상 면접을 실시하고, 실시간 과제를 위해 화면 공유를 요구한다. 또한 면접 이후 보고서를 통해 지원자의 실제 위치를 검증하며, 미국 외 지역에서 접속할 경우 ‘옐로/레드 플래그’로 분류한다.

지원자는 근무할 사무실을 직접 선택해야 하며, 면접 과정에서 AI 사용 시 탈락될 수 있다는 점에도 동의해야 한다.

경력 및 추천서 검증을 위해 최소 2명의 추천인을 요구하고, 그중 1명은 이전 상사 또는 관리자여야 한다. 과거 근무 이력과 이전 회사도 확인하며, 자택 주소 제출도 의무화했다.

접근 권한 통제를 위해 신규 직무가 민감 정보에 대한 고급 접근 권한을 포함하는지 여부를 사전 문서에서 확인하도록 했다.

입사 첫날에는 반드시 사무실에 출근해 장비를 수령하고 온보딩 교육을 받아야 하며, 모든 직무는 초기에는 온사이트 근무가 원칙이다. 이후 성과가 검증된 경우에만 하이브리드 근무가 허용된다.

웨이송은 “이 문제를 해결하기 위해서는 채용 프로세스를 재점검하고 HR과 긴밀히 협력하며, 각 대응 조치의 효과를 지속적으로 점검해야 한다”고 강조했다. 이어 “채용 시스템 자체가 잘못된 것이 아니라, 신뢰를 단계적으로 구축하는 방식으로 접근해야 한다”고 덧붙였다.
dl-ciokorea@foundryco.com

The fake IT worker problem CIOs can’t ignore

Hiring fake IT workers has been a growing problem in recent years — but it’s often a problem very few want to admit to. From Fortune 500 companies down to smaller organizations, remote hiring practices have been exploited to grant trusted access to individuals who are not who they claim to be creating an insider threat risk.

Estimates suggest there are thousands of fake IT workers operating across the US who are in a position to steal information, IP and data, outsource work offshore, carry out sabotage, or funnel money to foreign governments.

Amazon has identified and blocked more than 1,800 attempts by North Korea to secure IT roles — and the numbers are rising, according to its chief security officer, Steve Schmidt.

In some cases, individuals impersonate US employees for personal gain; in others, state-based operatives such as those from North Korean pose as IT workers for state financial gain and other nefarious purposes.

AI is now enabling deepfakes, more convincing video interviews, and rapid identity cycling.

Adversary tactics are also shifting, from fabricating profiles to purchasing legitimate American identities, Schmidt has warned.

“This is not a ‘recruiting scam’ in the traditional sense. It’s an insider-risk problem, where the adversary’s first move is to get hired,” says Tom Hegel, distinguished threat researcher at SentinelOne.

CIOs, CISOs, and other IT leaders need to be continually on guard against fake and fraudulent IT workers, but organizations can fall victim without realizing it.

How fake hires get through

There’s no single point of failure in the recruitment process. Fake and fraudulent IT workers conceal their identity, falsify their skills and experience, and move through interview and screening processes undetected.

SentinelOne has tracked roughly 360 fake personas and more than 1,000 job applications linked to North Korean IT worker operations, including attempts to apply for roles within the company itself.

According to Hegel, adversaries are increasingly deploying social engineering tactics and identity obfuscation at scale, and the hiring process is a prime entry point.

Synthetic or stolen identities are used to create resumes and online profiles; interviews are passed with the help of scripts, stand-ins, or AI-assisted responses; and background checks confirm only what’s presented to them.

“Fake job seekers now leverage AI tools to mimic legitimate candidates, creating synthetic identities that pass initial background checks, falsifying employment histories and even responding convincingly in interviews using real-time AI assistance,” Hegel says.

Flashpoint investigations have found malware-infected hosts containing HR and job-board logins, browser histories showing Google-translated coaching notes, remote-access “laptop farms” used to control corporate devices from overseas, and shell companies to prove reference checks for fabricated resumes.

Once they’re hired, credentials are issued, equipment is shipped, and access is granted — and they become a trusted insider. “The long-term risk isn’t just hiring a fake employee — it’s unknowingly opening your systems and sensitive data to malicious access,” he says.

What to do if you suspect a fake IT worker

When a CIO suspects a fake IT worker, next steps are important as the issue shifts from recruitment to insider risk management.

During his time at MongoDB, George Gerchow, IANS faculty advisor and Bedrock Data CSO, oversaw the investigation after the company detected it had unknowingly hired a North Korean IT worker.

It was first discovered after alerts that an individual was attempting to uninstall endpoint protections, including CrowdStrike Overwatch. “Overwatch then detected the laptop communicating with a North Korean IP address,” says Gerchow.

“That combination of tool tampering plus DPRK-linked traffic immediately signaled that this was not a typical new hire,” he tells CIO.

Mongo realized the fake worker used a stolen identity, paired with AI-generated resume content and scripted interview responses, to evade background checks that verify only the information provided and do not detect fraud.


It highlights a gap in many background checks. “They don’t detect fabricated work histories, synthetic identities, or recycled developer profiles, which is how this individual passed screening and interviews without raising formal flags,” he says.

The subsequent investigation found attempts to disable security tooling, establish persistence on the device, and probe for elevated access.

“Had they remained undetected, their access would have eventually expanded into our FedRAMP environment, which makes these fraud techniques especially high-risk,” Gerchow adds.

After the discovery, several yellow flags became obvious such as poor video quality and unclear visuals during interviews, a noticeably inconsistent accent between calls, and scattered interview feedback with no centralized review.

Another tell was a last-minute change to the laptop shipping address. “That’s a common shadow-worker tactic,” notes Gerchow.

With hindsight, Gerchow joined the dots and it became clear how the person had made it through to employment because any irregularities were treated in isolation.

“None of these individually would prevent a hire. However, because no one was responsible for aggregating subtle anomalies, the pattern wasn’t recognized until the endpoint alert fired,” he says.

When they were discovered, the team quickly isolated the device, revoked all credentials, conducted a full forensic investigation, and notified federal authorities. “We verified there was no data exfiltration or lateral movement,” he says.

The mitigation steps introduced included strengthening identity fraud screening in the hiring process, assigning a Yellow Flag owner to connect early signals, and enforcing zero access until trust is earned for new hires,


Gerchow also believes that behavioral telemetry post-hire is necessary, because behavior, not credentials, reveals impostors.

Mongo recommends organizations designate a reviewer in Security or HR to identify inconsistencies in the hiring process, such as poor video quality. “Also watch for AI-generated LinkedIn profiles, mismatched resumes and questionable changes in laptop shipping addresses,” he says.

“Use panel interviews and project-based evaluations to identify candidates who recycle stolen or fake developer identities, and start new hires without access to sensitive data or production environments,” he advises.

Then employ alerts if security agents (such IAM, EDR, VPN) are disabled before a new hire logs in, and test detection, escalation, and device recovery by simulating the hiring of a fake developer.

“And look for off-hours access, broad internal search activity and large-scale cloning of documents or code repositories,” he adds.

What IT leaders see on the inside

The problem of employment fraud is only expected to worsen, with Gartner predicting that one in four candidate profiles worldwide will be fake by 2028.

“The rise of fake and fraudulent job applicants has become an epidemic across organizations,” says David Weisong, CIO of Energy Solutions.

Weisong says attackers consistently target high-access technical roles such as DevOps, systems administrators, data engineers, and database administrators, where successful hires can gain deep visibility and control over core systems.

“These are the roles with the keys to the castle,” Weisong says. “If you’re trying to gain access, they’re far more valuable than a standard developer position.”

Operating in a regulated energy market, Energy Solutions is contractually required to employ a US-based workforce and keep data within US jurisdiction.

Weisong has first-hand experience with detecting fake IT workers and wants to share his advice with other IT leaders. One of the earliest warning signs was a sudden, abnormal surge in applications — hundreds arriving within hours, far out of proportion to the company’s brand profile, pointing to automated or coordinated activity.

During the interview stage, identity switching was observed. “We saw cases where one person passed the phone screen, a different person showed up on Zoom, and sometimes a third appeared later — all under the same name and resume,” Weisong says.

Part of the problem is that standard hiring practices validate information and skills in isolation. “Traditional background checks only verify the information provided and do not detect fraud,” Weisong also notes.

The uncomfortable reality for some CIOs is that the work may be completed to a high standard and detection comes from signals, not performance.

However, fake IT workers create business and compliance risk as much as security risk, exposing organizations to contractual breaches, regulatory consequences, and loss of client trust — particularly in regulated industries.

Weisong says fake IT workers create business and compliance risk as much as security risk, exposing organizations in regulated industries to contractual breaches, regulatory scrutiny, and loss of client trust.

Combating the problem of fake IT workers

Amazon is using AI-based tools with human oversight to identify unusual contact information, as well as fake academic institutions and companies in resumes, according to Schmidt. Security teams will flag LinkedIn profiles that look suspicious, require more in-person interviews and in-office attendance, monitor computer usage and quality of work, and authenticate with a physical token.

He has also said that IT and HR need to collaborate on hiring to combat the problem.

“It’s actually a lot cheaper for the HR organization if we discover the problem up front,” Amazon’s Schmidt told Fortune.

The shift required, says SentinelOne’s Hegel, is treating hiring decisions as an access control problem rather than a recruitment task. “Stop treating identity as a one-time HR checkbox and start treating remote hiring like you would grant privileged access,” he says.

In the wake of his experience, Weisong instituted a raft of changes to its applicant tracking system and across the organization’s internal systems and processes.

When advertising for positions, they make it clear that candidates applying for technical positions understand the expectations and consequences outlined in all written communication. “Additionally, removing the term ‘fully remote’ from our hiring practices has significantly reduced opportunities for fraud and for applicants applying from outside the US,” he says.

“While a ‘zero-trust’ approach would be ideal for all hiring, we cannot allow it to impede the process or discourage legitimate candidates from applying. Instead, we need sufficient countermeasures to prevent automated and fraudulent applicants from reaching the pipeline in the first place,” he adds.

To control the large volume of applications, many of which are bots, Energy Solutions job listings now have strict CAPTCHA settings, referral bonuses help draw on employee networks, and there’s a 90-day satisfactory performance review for new hires.

During the screening process, interviews are conducted via video not phone, and applicants must share their screen for live challenges. A post-video interview report allows them to verify the exact location of applicants after screening and interview meetings. If a candidate is outside the US, it’s treated as a Yellow/Red flag.

Applicants must select which office they want to work from and they must acknowledge they understand use of AI during interviews will result in disqualification.

To verify references and employment history, they require two references, with one a former supervisor or manager. Employment history is checked, including previous employers, and full home address must be provided.

To guard access, a question has been added to the job kick-off form that indicates whether a new role will have elevated access to confidential or sensitive information.

The first day on the job requires new hires to come into an office to pick up equipment and undertake training and onboarding. All roles must be onsite, with the option to go hybrid after satisfactory performance.

Combating the problem, says Weisong, requires reviewing hiring processes, partnering closely with HR, and monitoring the effectiveness of each countermeasure. For CIOs, the lesson is not that hiring is broken, but that trust must be earned progressively.

Time to Rethink Privileged Access for Machines and AI Agents

For years, Identity and Access Management (IAM) and Privileged Access Management (PAM) have been treated as foundational and a solved security challenge. Organizations deployed vaults, enforced policies, and checked the compliance box for their privileged users.  Fast forward to today, and that model no longer holds up.    What’s emerging now is not an incremental shift, but a structural one. Identity is no longer centered on […]

The post Time to Rethink Privileged Access for Machines and AI Agents appeared first on 12Port.

The post Time to Rethink Privileged Access for Machines and AI Agents appeared first on Security Boulevard.

Your Biggest Security Risk Might Not Be Human

Beyond your human workforce, a vast and growing population of non-human identities—applications, service accounts, cloud instances, and now, autonomous AI agents—operates with significant access, often in the shadows. This explosion of “unseen” identities is creating a critical governance gap and a new, often unmanaged, vector for risk.

As one of our customers aptly put it, there is a palpable tension in the boardroom: a mandate to innovate at full speed with technologies like AI, set against the imperative to avoid the kind of security incident that lands the company on the front page. The pressure to innovate is immense, but the ROI from new technology can’t be realized until it’s in production, and it can’t be put into production without proper governance.

Even before the widespread adoption of AI agents, security teams were already struggling to manage the sheer volume and variety of identities. Now, the proliferation of machines and intelligent agents has pushed this challenge to a breaking point. A complete identity strategy must now extend beyond the human workforce to encompass every facet of this new identity landscape.

While these non-human identities represent a new frontier, governing them doesn’t require starting from scratch. The most effective approach is to bring these new identity types under the umbrella of your existing, proven identity governance framework. Once aggregated into a centralized model, all the shared services—certification, workflow automation, and access reviews—that have been honed for years can be applied to them, creating a unified view and consistent control.

To manage this complex and dynamic environment, security leaders must move toward a model of adaptive identity. This approach allows for the dynamic adjustment of access policies for all identities based on real-time context and risk. It’s about having the intelligence to understand not just who or what is accessing your systems, but also why, when, and how.

Confidence in your security posture is the bedrock of agility; without it, the pace of modern business is unsustainable. From a scaling perspective, automation is essential. Gaining clear visibility and automated control over all your identities, both human and non-human, is the only way to innovate safely and secure the unseen.

To discover actionable strategies for securing non-human identities and safely navigating AI innovation, register for our free global virtual broadcast, IdentityTV 2026, on May 19.

What CISOs need to get right as identity enters the agentic era

Identity has always been central to security, but the proliferation of AI agents is rapidly changing the challenge of managing and securing identity, spurring CISOs to rethink their identity strategies — even how it is defined.

“Identity is now both a control surface and an attack surface. We’ve had non-human identities as API keys, tokens, service accounts, but now we have agents, and that’s a new class,” says Dustin Wilcox, senior VP and CISO at S&P Global.

The challenge is attributing actions to non-human identities because the typical signals don’t apply. “The techniques to identify a person, like the telemetry of how they use the keyboard, we won’t be able to do that when it’s an agent that’s working entirely digitally,” Wilcox tells CSO.

And as agents proliferate, it becomes difficult for CISOs to maintain a complete picture of how many exist, what they’re used for, and what they’re authorized to do.

“With a human identity, you can validate access needs directly. With service accounts, and now with agents, that clarity is harder to achieve,” says Docusign CISO Michael Adams.

“Treating them as if they fit existing models can create gaps in visibility and control. At the same time, AI systems are contributing to rapid growth in non-human identities, including the creation of new credentials and tokens, which many inventory processes weren’t designed to track,” he adds.

“And on the human side, generative AI is making social engineering more convincing, eroding some of the behavioral signals defenders have historically relied on. The result is an expanding attack surface at the same moment traditional indicators are becoming less reliable,” Adams tells CSO.

The advice for CISOs is to adopt an identity-first security model that treats identity as the foundational layer of the security architecture.

“Every access decision flows through identity and is continuously verified, not just checked at the door,” says Adams.

Identity becomes the primary control plane

CISOs are now managing a new class of identities that includes copilots, autonomous agents, and AI-powered workflows that don’t fit neatly into existing frameworks. And they can access systems, take actions, and make decisions at machine speed.

Wilcox and Adams are speaking at the CSO Cybersecurity Awards & Conference, May 11–13. Reserve your place.

As a result, Adams says CISOs will increasingly need to adopt an identity-centric security architecture and there are several key tenets to consider.

Build a strong foundation before layering on complexity. The instinct when modernizing an identity program, says Adams, is to reach for sophisticated tooling. Instead, his advice is to get the fundamentals in place — clean directories, enforced least privilege, and reliable offboarding processes.

“Organizations that jump to continuous verification without establishing basic identity hygiene may find themselves building on an unstable foundation,” he says.

Design for the new class of identities. When designing role models and access policies, the temptation is to mirror existing structures.

“That often carries years of permission creep into a new architecture. Starting from least privilege rather than from legacy helps ensure users receive only the access required for their job functions,” he says. “It’s important to challenge ‘it’s always been done this way’ where appropriate.”

Get your non-human identity inventory in order. Build a full inventory of non-human identities and include who is responsible for each identity, and what each one is authorized to do. Do this before any more agents are operating.

“This is as much a governance challenge as a technology one,” he notes.

Treat MFA as a starting point, not a destination. The identity roadmap needs to include phishing-resistant alternatives to SMS or push-based MFA. Least privilege, micro-segmentation, and continuous monitoring are part of the playbook.

“Assume credentials may be compromised and architect accordingly,” Adams advises.

AI and the shifting security balance

Identity systems have long been targets for attack. But as identity becomes the primary control plane, the risk becomes more concentrated and requires a different approach.

“I’d encourage every CISO to think deeply about the intersection of identity and AI,” says Adams, adding that systems need to be redesigned around the principle of intent instead of actual behavior to ensure agents operate within appropriate boundaries.

“That requires behavioral monitoring and real-time access evaluation — capabilities many organizations are still building toward,” he notes. “That’s the work ahead.”

Wilcox is ultimately optimistic that AI offers security practitioners more tools to combat malicious actors. If CISOs can get this right, it’s a way to level the playing field with the attackers in a way not previously available.

“We’ve had this asymmetric playing field where they’ve had the advantage for as long as I can remember. Now we can use AI both strategically and tactically to improve our defenses,” he says.

Agentic AI is rewriting the identity security playbook in real-time, and your peers are already adapting. Hear Dustin Wilcox, Michael Adams, Renee Guttmann, and other leading CISOs share what’s actually working at the CSO Cybersecurity Awards & Conference, May 11–13. Secure your seat before it fills up.

英 NCSC, 기업에 패스키 전환 촉구 “피싱 공격 차단에 효과적”

영국 국가 사이버보안센터(NCSC)가 기업이 소비자에게 제공하는 기본 인증 방식으로 패스키를 채택할 것을 권고했다. 산업 전반의 기술 발전으로 패스키가 비밀번호보다 더 안전하면서도 사용자 친화적인 대안으로 자리 잡았다는 판단에서다.

NCSC는 23일 블로그를 통해 “이제 패스키를 개인과 기업 모두를 위한 주요 인증 수단으로 권장할 수 있는 수준에 도달했다”고 밝혔다. 이어 “패스키는 소비자의 첫 번째 로그인 선택지가 되어야 한다”며 “비밀번호는 현대 환경에서 더 이상 충분한 복원력을 갖추지 못했다”고 지적했다.

또 “패스키는 온라인 계정 로그인 방식의 새로운 형태로, 사용자가 비밀번호를 입력하는 대신 승인만 하면 되도록 대부분의 과정을 자동 처리한다”며 “이로 인해 더 빠르고 간편하게 사용할 수 있고, 사이버 공격자가 침해하기도 훨씬 어렵다”고 설명했다.

NCSC는 패스키를 지원하는 모든 환경에서 이를 적극 활용해야 한다고 강조하며, 패스키가 피싱 공격에 강하고 비밀번호 재사용으로 인한 위험을 제거한다고 밝혔다.

피싱에 강한 인증 방식에 초점

이번 가이드라인은 실제 공격 환경에서 인증 방식이 어떻게 작동하는지를 분석한 결과를 기반으로 한다.

NCSC는 피싱, 자격증명 재사용, 세션 하이재킹 등 주요 공격 기법을 중심으로 인증 수단을 평가했으며, 자격증명이 생성·저장·사용되는 전 과정에서 어떻게 노출되는지를 종합적으로 분석했다고 밝혔다.

NCSC는 “패스키는 피싱 공격에 강하며 비밀번호 재사용에 따른 위험을 제거한다”고 재차 강조했다.

또한 별도의 기술 문서를 통해 기존 인증 방식에 대해서도 평가를 내놨다. 비밀번호와 일회용 코드(OTP)를 결합한 방식조차 “본질적으로 피싱 공격에 취약하다”고 지적했다.

반면 FIDO2 기반 패스키는 “현실에서 발생하는 대부분의 자격증명 공격에 대해 기존 다중인증(MFA)과 동등하거나 그 이상의 보안 수준을 제공한다”고 분석했다.

다만 NCSC는 해당 분석이 기업 내부 인증 환경에 그대로 적용되는 것은 아니라고 설명했다. “이 문서의 상당 부분은 직원의 싱글사인온(SSO) 인증과 같은 기업 환경에도 적용될 수 있지만, 위협 모델과 사용 시나리오가 다르기 때문에 기업 리스크 평가를 위한 용도로 작성된 것은 아니다”라고 덧붙였다.

공격 모델을 바꾸는 패스키

NCSC는 패스키가 기존 인증 구조의 핵심 위험 요소인 ‘공유된 비밀(shared secret)’ 의존성을 제거함으로써 보안 위험을 낮춘다고 설명했다. 인증 정보를 특정 서비스에 강하게 결합하는 방식이기 때문에 공격자가 이를 가로채 재사용하는 것이 불가능하다는 것이다.

이에 따라 자격증명 재사용 공격이나 중계(릴레이) 공격을 원천적으로 차단할 수 있다. NCSC는 패스키가 사용자 기기에 저장된 암호화 키 쌍을 기반으로 작동하며, 생체인식이나 PIN과 같은 기기 기반 인증과 결합된다고 밝혔다.

사용자 인증 방식의 구조적 전환

이번 가이드라인은 고객 대상 온라인 서비스를 제공하는 기업들에게 사용자 인터페이스 수준의 인증 방식 변화를 요구하는 신호로 해석된다.

글로벌 시장조사업체 포레스터(Forrester)의 수석 애널리스트 마들레인 반 더 하우트는 “이번 변화는 점진적인 인증 업그레이드가 아니라 근본적인 아키텍처 전환”이라며 “비밀번호와 다중인증(MFA) 조합을 넘어, 피싱 저항성을 중심으로 한 새로운 인증 기반으로 이동하는 것”이라고 설명했다.

이어 “패스키는 공유된 비밀 대신 기기 기반 암호화 인증을 사용해 자격증명 탈취 위험을 제거한다”며 “이를 단순한 인증 수단 교체로 접근하면 투자 부족으로 이어질 수 있지만, 신원 관리 현대화 기회로 인식하면 경쟁력을 확보할 수 있다”고 덧붙였다.

NCSC는 기업이 인증 체계를 설계할 때 로그인뿐 아니라 계정 복구와 대체 인증 수단까지 포함한 전체 사용자 여정을 고려해야 한다고 강조했다. 패스키 도입으로 비밀번호 의존도는 줄어들지만, 비밀번호 재설정이나 계정 복구 절차가 취약할 경우 여전히 보안 위험이 발생할 수 있다는 지적이다.

여전히 남아 있는 도입 과제

NCSC는 패스키가 아직 모든 서비스에서 지원되는 것은 아니라고 밝혔다. 이에 따라 패스키를 사용할 수 없는 환경에서는 비밀번호 관리 도구와 다중인증을 병행할 것을 권장했다.

NCSC는 “특정 서비스가 패스키를 지원하지 않는 경우, 강력한 비밀번호를 생성할 수 있는 비밀번호 관리자를 활용하고 2단계 인증을 계속 사용하는 것이 바람직하다”고 설명했다.

반 더 하우트는 특히 다양한 플랫폼과 사용자 환경을 동시에 운영하는 기업에서 구현 난도가 높을 것으로 내다봤다. 그는 “레거시 시스템과 분산된 신원 관리 환경이 상당한 장애 요인으로 작용한다”고 분석했다.

또한 머신 계정 등 비인간 식별체에 대한 고려도 필요하다고 강조했다. “머신 아이덴티티 계층을 고려하지 않은 패스키 전략은 새로운 보안 공백을 만들 수 있다”고 말했다.

아울러 기기 요구사항과 계정 복구 절차 역시 패스키 도입 방식에 영향을 미칠 수 있다고 덧붙였다.

전환기에는 ‘하이브리드 인증’ 불가피

업계에서는 단기간 내 비밀번호를 완전히 대체하는 것은 현실적으로 어렵다는 분석이 나온다.

마들레인 반 더 하우트 포레스터 수석 애널리스트는 “향후 수년간은 패스키와 기존 인증 방식이 병행되는 하이브리드 모델이 지속될 것”이라며 “기업들은 패스키와 전통적인 인증 방식을 동시에 지원해야 할 것”이라고 전망했다.

이어 “이 기간 동안 기업은 다양한 로그인 옵션을 통합 관리해야 하며, 특히 대체 인증 수단이 전체 보안 수준을 약화시키지 않도록 설계하는 것이 중요하다”고 설명했다.

NCSC 역시 패스키를 사용할 수 없는 환경에서는 기존의 강력한 인증 체계를 유지할 것을 권고했다.

비밀번호 없는 로그인 전환 가속

이번 가이드라인은 소비자 인증 영역에서 비밀번호 의존도를 줄이려는 흐름을 더욱 강화하는 정책 신호로 해석된다.

반 더 하우트는 “이번 지침은 보안 책임자들이 벤더나 내부 이해관계자와의 논의에서 보다 강한 추진력을 확보할 수 있게 한다”고 평가했다.

NCSC는 “피싱 저항성을 갖춘 인증 방식으로 전환할 경우, 특히 사용자 로그인 정보에 의존하는 서비스에서 주요 사이버 침해 원인을 크게 줄일 수 있다”고 강조했다.
dl-ciokorea@foundryco.com

Dynamic privilege: Balancing access and security

Static access is one of the most persistent risks in enterprise security. As employees move across roles and projects, permissions accumulate and very few are removed. What starts as operational convenience becomes exposure. Accounts retain access they no longer need and visibility erodes.

The result is an expanding attack surface. The risk is most pronounced in business applications, where the line between privileged and non-privileged access is often unclear. Organizations manage millions of entitlements and manual oversight often breaks down. Reviewing access alone can take years, making ongoing governance nearly impossible.

At the same time, not all access carries equal risk. Viewing regional data is not the same as downloading global financial forecasts. Yet traditional models often treat both as binary decisions. That lack of nuance creates a gap. Identity and security teams cannot confidently answer who should have access to what, and why.

Moving beyond role-based access

Dynamic privilege addresses this by treating access as something that must be evaluated continuously. Instead of assigning static permissions through roles, it introduces context. Access decisions are based on who is requesting access, what they are accessing, and the conditions surrounding that request.

In practice, this includes automated discovery and classification of entitlements, just-in-time access, real-time validation, and continuous monitoring. This model, often described as Privilege Security Posture Management (PSPM), shifts governance from static assignment to active control. The question changes as well. It is both about who should have access, and who currently has access to what matters most.

What actually drives better decisions about access and where things break down

Dynamic access depends on signals, but only a subset meaningfully improves outcomes. The most important signals fall into three categories: identity, entitlement, and session context. Identity factors include role, exposure to threats, and unusual behavior patterns. Entitlement factors reflect the sensitivity and risk level of the access itself. Session context includes device health, network type, and location. Combined, these inputs form a risk score that supports real-time decisions based on actual conditions, not assumptions.

The challenge of dynamic access often occurs in execution. The volume of entitlements overwhelms manual processes. Without automation, organizations cannot keep pace. Role-based models also struggle at scale. Roles often mix privileged and non-privileged access, leading to complexity that is difficult to govern.

No single stakeholder has full visibility. Managers, application owners, and identity teams each see only part of the picture. Access paths further complicate matters. A user may gain entry through multiple routes, making it difficult to fully remove access and enforce least privilege.

Security without friction

Dynamic access raises a natural concern: will it disrupt users? In practice, the goal is the opposite. Policy checks are embedded into existing workflows. Access decisions happen in the background, allowing users to continue working without interruption.

When additional steps are required, such as just-in-time activation, they are designed to be fast and tied to a specific need. Continuous evaluation ensures access is only interrupted if risk conditions change.

Compliance is the baseline for organizations concerned about access. The real outcome is measurable risk reduction and operational efficiency. That includes eliminating standing privileges, reducing the time required to identify risk, improving visibility into high-risk access, and lowering the frequency of access-related incidents. It also shifts organizations from reactive control to continuous oversight.

Static access assumes stability, but modern environments are not stable. That’s why dynamic privilege is needed — it reflects that reality, treating access as something that must be evaluated continuously and controlled in real time.

To discover how you can reduce identity risk using dynamic privilege and real-time access controls, register for SailPoint’s free virtual broadcast, IdentityTV 2026, on May 19.

A letter from our CISO, Rex Booth

Like many of you, I’ve been in the cyber domain for what feels like a long time. Long enough to remember when a compromise of your company was considered catastrophic. It was a shameful moment, to be hidden from public knowledge at all costs. When I was at Mandiant in the early teens, many of our clients swore us to secrecy lest word get out that they were vulnerable to the focused aggressions of a nation state. It now seems almost quaint that such an obvious conclusion would need to be hidden.
 
Thankfully, the ensuing years have removed much of that shame. The mantra of “it’s not a matter of if, but when” has become commonplace.  We all fight against such events and are reluctant to embrace the eventuality, but our CEOs and boards are increasingly aware that this is just another business risk that needs to be managed.
 
But there are two elements of a compromise that can still resurrect that sense of shame and bring lasting negative consequences to a CISO and their company.
 
The first is your ability to recover.  
 
It’s one thing to suffer a compromise. But if and when it happens, you need to demonstrate your readiness to recover and minimize the impact. The longer you linger in a down state, the faster forgiveness and sympathy disappears.
 
The second is the perception of negligence.  
 
The market and our stakeholders may understand the difficulty of withstanding a concerted effort to breach our defenses. But if a post-breach analysis shows we failed to address known vulnerabilities or implement basic controls, our credibility plummets, and the reputation of our company and ourselves can suffer a lasting impact.
 
The emergence of AI makes both elements more challenging. AI is expanding our collective tech footprint at a speed we’ve never seen before, potentially exposing us to both the recovery and negligence risks in unexpected ways. Maintaining visibility and appropriate control – all while enabling the tremendous promise it brings – is the challenge of our careers. This is the moment that will delineate those of us who can strike the right balance between security and enablement and those who retreat to old, restrictive models.
 
We can’t do this alone. Exciting technology is emerging to manage the exponential growth of identities, supporting adaptive identity programs that provide visibility and control needed to ensure the appropriate use of AI. Ultimately the CISO shouldn’t just be a preventive function, but an aspirational one as well, allowing the creative and augmenting power of AI to flourish in ways that minimize risk. 

As we navigate this pivotal moment in our industry, the tools we choose will define our ability to balance innovation with security. At SailPoint, we are committed to equipping CISOs with adaptive identity solutions needed to manage the complexities of AI and beyond. Together, we can embrace the future with confidence, ensuring that security becomes a catalyst for growth rather than an operational constraint.

Join us at IdentityTV where we’ll delve deeper into how adaptive identity solutions can help drive innovation while navigating the complexities of modern security.

Identity in the SOC: From decision latency to decisive action

For many Security Operations Centers, threat detection is faster than ever. The problem is that the decisions that follow are not. Every alert forces a critical, time-consuming question that detection tools alone cannot answer: “Who is this, and does it matter?”

Modern attacks thrive in this moment of decision latency. With industry reports indicating that over 90% of all breaches stemming from identity-based attacks, attackers no longer need to break in—they use the keys. They exploit the seams between security tools and teams, where a lack of shared identity context creates the ‘identity ambiguity gap’: the operational void where attackers find the time to succeed. Closing this gap requires a framework that bridges this divide built on three pillars: Signal, Context, and Action (SCA).

Signal: Turning noise into clarity

A blurry signal is just noise. An alert for a ‘suspicious login,’ for example, means little without knowing if it involves a contractor, a domain administrator, or a dormant service account. By enriching alerts with core identity attributes at detection, security teams can instantly clarify the “who” behind the “what,” focusing on real threats instead of shadows.

Context: Building the bridge to understanding

A clear signal identifies who is involved, but context reveals what they can do and why it matters. This essential layer transforms a raw alert into actionable insight, eliminating the decision latency that gives attackers the upper hand. Without it, analysts waste time piecing together an identity’s permissions, roles, and potential blast radius.  A single source of identity truth delivers real-time answers to critical questions:

  • What is the true blast radius of this identity?
  • What sensitive data can it access, directly and indirectly?
  • Does it have dormant or high-risk permissions?

This eliminates guesswork, empowering analysts to act with confidence.

Action: Executing a swift, surgical response

Clarity of context empowers decisive action. A confident understanding of an identity’s true blast radius eliminates panic-driven guesses. Instead of disabling an account and disrupting business, the SOC can execute precise responses, such as revoking high-risk permissions or isolating a compromised identity.  Automated, precise actions on established risks close the decision latency gap, containing threats at machine speed without operational drag.

Conclusion

The seams between identity and security are where modern attacks are won and lost. For security leaders, waiting for manual investigation in the face of automated threats is no longer an option. By adopting the SCA framework, organizations can transform ambiguity into clarity, enabling their teams to act with speed and precision. This strengthens security posture, ensures business alignment, and drives operational efficiency.

Explore more strategies for bridging the gap between identity and security at IdentityTV, where industry leaders share insights to empower decisive action in the SOC.

Router reality check: 86% of default passwords have never been changed

Misconfigurations remain a popular compromise point — and routers are leading the way.

According to recent survey data, 86% of respondents have never changed their router admin password, and 52% have never adjusted any factory settings. This puts attackers in the perfect position to compromise enterprise networks. Why put the time and effort into creating phishing emails and stealing staff data when supposedly secure devices can be accessed using “admin” and “password” as credentials?

It’s time for a router reality check.

Rising router risks

Routers allow multiple devices to use the same internet connection. They accomplish this goal by directing traffic — internal devices are routed along the most efficient path to outside-facing services, and incoming data is sent to the appropriate endpoint.

If attackers manage to compromise routers, they can control both what comes out of and what goes into your network. This introduces risks such as:

The nature of router attacks also makes them hard to detect. This is because cyber criminals aren’t forcing their way into routers or taking circuitous routes to evade security defenses. Instead, they’re taking advantage of overlooked weak spots to access routers directly, which means they aren’t raising red flags.

Consider a router with “admin” as the login and no password. A few simple guesses get attackers into router settings without triggering a security response since they haven’t breached a network service or compromised an application. Instead, they’ve accessed routers the same way as staff and IT teams.

Explore IBM Instana

Exploring the defensive disconnect

Companies recognize the need for robust cybersecurity. According to Gartner, spending on information security will grow 15% in 2025 to reach $212 billion. Common investment areas include endpoint protection platforms (EPPs), endpoint detection and response (EDR) and the integration of generative AI (gen AI). Routers, however, are often overlooked.

For example, 89% of respondents have never updated their router firmware. The same number have never changed their default network name, and 72% have never changed their Wi-Fi password.

This is problematic. A recent report found that popular OT/IoT router firmware images were outdated and contained exploitable N-day vulnerabilities. The report found that, on average, open-source components were more than five years old and were four years behind the latest release.

As noted by GovTech, meanwhile, an attack on a Pittsburgh-area water authority succeeded in part because the default password to its network was “1111”. Other common passwords include “password” and “123456;” in some cases, routers have no passwords. All attackers need is the login credential — which is often “admin” — and they have full access to router functions.

Even more telling is the fact that router security is getting worse, not better. Consider that in 2022, 48% of respondents said they had not adjusted their router settings, and 16% had never changed the admin password. In 2024, over 50% of routers were still running on factory settings, and just 14% had changed their password.

By spending more on security tools but not changing default configurations or updating router firmware, businesses are closing the doors but leaving the windows wide open.

Minimizing misconfiguration mistakes

So, how do companies minimize the risk of misconfiguration mistakes?

It starts with the basics: Change passwords regularly, update firmware and ensure that routers aren’t left on factory settings. Simple? Absolutely. Common? As survey data indicates, not so much.

In part, the disconnect between router risks and security realities stems from the sheer volume of cyberattacks. For example, 2023 saw 94% of companies hit by phishing attacks, and as noted by the IBM Cost of a Data Breach Report 2024, the average cost of a data breach is now $4.88 million, up 10% from 2023 and the highest ever reported. This puts cybersecurity teams on the defensive and on high alert for common attack vectors such as phishing, smishing and the use of “shadow IT” applications that haven’t been vetted or approved.

As a result, routers can slip through the cracks. The first step in solving this problem is creating a regular update schedule. Every four to six months, schedule a router review — put it in a shared calendar, and make sure all security staff know it’s going to happen. When the designated day comes, update firmware where possible and change login and password details. It’s also worth establishing a weekly schedule to review router traffic for any odd behaviors or unexpected login requests.

Shoring up security

While basic cyber hygiene helps lower the risk of router attacks, shoring up security requires a more in-depth approach.

The first step is finding and securing every router on your network. Given the increasingly complex nature of enterprise networks, the easiest way to accomplish this goal is by using automation. Solutions such as IBM SevOne Automated Network Observability provide pre-built workflow templates for IT teams to identify connected devices, collect performance data and make data-driven decisions.

Companies also need to consider what happens when a router compromise occurs. Despite best efforts by security teams, the growing number of end points means it’s only a matter of time until attackers manage to find unprotected routers or circumvent existing defenses.

Effective response requires effective incident management. Solutions such as IBM Instana offer full-stack visibility, one-second granularity and three seconds to notify, giving teams the information they need when they need it to reduce security risks.

Bottom line? Failure to monitor and update router settings can open the door to compromise. To solve the problem, teams need a router reality check. By combining security hygiene best practices with intelligent automation solutions, enterprises can keep unauthorized users where they belong: 0utside protected networks.

The rising risk of router attacks, paired with a growing list of unreasonable expectations, creates complex challenges for security teams. The solution? Unreasonable observability. Learn more on IBM Instana and how it can help.

The post Router reality check: 86% of default passwords have never been changed appeared first on Security Intelligence.

❌