참고 자료 · 19

엔터프라이즈 배포 전 브라우저 확장 프로그램 검토

권한, 사이트 액세스, 업데이트 및 확장 프로그램 제거 가능성 평가

업데이트됨 · 20 min

모니터에 추상 권한 카드와 사이트 연결이 표시된 가상의 무인 확장 프로그램 접근 검토 작업대, 검은 책상과 금빛 조명 AI로 생성한 편집용 일러스트

이 가이드가 달성하는 목표

  • 확장 프로그램 인벤토리
  • 권한 검증
  • 업데이트 제어
  • 제거 준비

빠른 확인

  • 어떤 특정 작업에 확장 프로그램이 필요합니까?
  • 어떤 사이트와 데이터에 액세스할 수 있습니까?
  • 권한이 적절합니까?
  • 누가 새 버전을 모니터링하나요?
  • 영향을 받는 모든 엔드포인트에서 어떻게 비활성화할 수 있나요?

단계별 방법

  1. 1

    사용량 인벤토리

    설치된 확장 프로그램, 식별자, 버전, 브라우저, 사용자, 팀 및 소유자를 수집합니다. 중복 항목과 책임 소유자가 없는 확장 프로그램을 찾습니다.

    결과물: 날짜가 기록된 확장 프로그램 및 소유권 등록부

  2. 2

    필요성 정의

    각 확장 프로그램을 실제 작업 및 사용 가능한 대안과 연결합니다. 권한을 결정하기 전에 관련된 데이터와 사이트를 정의합니다.

    결과물: 사용 및 범위 개요

  3. 3

    액세스 검토

    호스트 액세스, 탭, 저장소, 클립보드 및 기타 요청된 기능에 대한 매니페스트 및 권한 경고를 읽습니다. 필수 권한과 선택적 권한을 구분합니다.

    결과물: 정당화되거나 축소 가능한 권한 표

  4. 4

    게시자 및 변경 사항 확인

    게시자, 배포 소스, 개인정보 보호정책 및 버전 변경 사항을 문서화합니다. 단순히 스토어에 존재한다는 사실만으로는 이 검토를 대체할 수 없습니다.

    산출물: 출처 기록 및 재평가 트리거.

  5. 5

    제어 기능을 포함한 배포

    적절한 프로필과 데이터로 확장 프로그램을 테스트한 후 관리되는 브라우저에 대한 승인 목록 또는 차단 규칙을 설정합니다.

    산출물: 결정, 배포 설정 및 담당자.

  6. 6

    종료 계획 수립

    사고 발생 시 신속한 비활성화, 제거, 영향을 받는 엔드포인트 식별 및 잠재적으로 노출된 데이터 처리 준비.

    산출물: 테스트 완료된 제거 절차.

이해하고 계산하고 판단하기

확장 프로그램 권한: 기능, 범위, 활성화 시점 구분하기

Chrome Manifest V3에서 권한 수는 보안 점수가 아닙니다. API 기능, 대상 사이트, 접근 권한이 부여되는 시점을 구분하세요.

activeTab은 사용자의 명시적 동작 후 임시 접근을 제공합니다. 같은 출처 내 이동에서는 유지될 수 있으며 출처 변경이나 탭 종료 시 취소됩니다. 브라우저의 제한된 페이지는 제외됩니다.

지표와 근거

지표해석필요한 근거
activeTab 사용자 호출 후 임시 접근 호출 동작과 출처 변경 시 취소 확인
scripting 스크립트를 삽입하는 기능 호스트 권한 또는 activeTab을 통한 페이지 접근도 필요
content_scripts.matches 콘텐츠 스크립트의 사이트 패턴 permissions, host_permissions와 별도로 검사

관리 지표

지표측정 대상첫 번째 조치
범위소유자와 목적이 문서화된 확장 프로그램소유자가 없는 설치 문제 해결
정당한 접근 권한 부여필수 기능에 연결된 권한과도한 접근 권한 축소 또는 거부
변경 사항 검토광범위한 배포 전 중요 버전 평가위험한 업데이트 일시 중지
제거 테스트 완료비활성화 테스트 대상 엔드포인트배포 격차 및 예외 수정

일반적인 실수

  • 스토어 등록을 보안 승인으로 간주
  • 이유 없이 모든 사이트에 대한 접근 권한 허용
  • 개인 프로필에서 누락된 확장 프로그램
  • 업데이트 후 권한 검토 실패

자주 묻는 질문

인기 있는 확장 프로그램은 안전한가요?

인기도만으로는 사용에 필요한 권한, 접근 가능한 데이터 또는 변경 사항을 결정할 수 없습니다.

모든 확장 프로그램을 금지해야 하나요?

비례적인 정책은 필요성, 접근 권한 및 관리되는 브라우저 컨텍스트를 평가합니다.

언제 재평가해야 합니까?

중요한 권한, 소유권, 기능 또는 버전 변경 후 및 정기적인 시스템 점검 시.

확장 프로그램: 권한과 접근

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

Reading a manifest helps prepare an extension review: which APIs are requested, for which sites, and when? A declaration describes requested scope. Effective access also depends on granted permissions, browser settings, policies and executed code.

Editorial selection of 20 Chrome permissions, with names checked against official documentation on 23 October 2026. Capabilities and questions are CIE synthesis. This is neither the complete permission list nor an official risk scale; it does not automatically apply to Firefox or every Edge version.

Five declarations with different meanings

Five declarations with different meanings
Manifest fieldWhat it declaresCIE review question
permissionsRequired API permissions.Which function justifies each capability? No warning does not mean no access.
optional_permissionsAPI permissions requestable at runtime, subject to API restrictions.Which permissions were actually granted, and can the optional feature be removed?
host_permissionsHost patterns requested for capabilities that use them.Can hosts be narrowed? In this field, the path does not restrict access to a directory.
optional_host_permissionsScope within which host access can be requested at runtime.Declared scope is not a list of sites already authorised.
content_scripts.matchesPatterns for static content scripts.Also read exclusions, globs and frame options; this differs from programmatic injection.

Google Chrome · Declare permissions · Documentation consulted 2026-10-23; browser behaviour remains version-dependent

Google Chrome · Permissions API · Documentation consulted 2026-10-23; browser behaviour remains version-dependent

20 permissions: capabilities and evidence to review

20 permissions: capabilities and evidence to review
Chrome permissionDocumented capability · CIE synthesisOperational review · CIE
activeTabTemporary access to the invoked tab after a user gesture; navigation to another origin or closing the tab revokes it.Test invocation and revocation; this is not standing access to every site.
scriptingProgrammatic JavaScript or CSS injection, with host access or activeTab as an additional requirement.Justify target pages and actions; this permission alone does not supply host scope.
tabsAccess to sensitive tab properties; most tab-management features do not require this permission.Check the need for URLs and titles; do not equate tabs with reading every page’s content.
storageExtension-specific storage with distinct areas and behaviours.Identify retained data, local/sync/session use and context access; assess secret handling separately.
cookiesCookie inspection and modification with host permissions for the relevant sites.Limit sites and test required operations; document partitioned-cookie handling where relevant.
webRequestRequest observation with host permissions; webRequestBlocking is a separate permission restricted in Manifest V3.Distinguish observation from blocking; in V3 check the policy-installed extension exception.
declarativeNetRequestDeclarative network rules; some blocking-type actions have implicit access.Review rules and actions; redirects and header modifications have their own host requirements.
declarativeNetRequestWithHostAccessThe same family of declarative rules, with host access required for every action.Compare this variant with actually granted hosts; the permission name alone does not establish access.
downloadsProgrammatic download management through the dedicated API.Justify initiation, search or manipulation and inspect actual use; this manifest reader downloads nothing.
historyBrowser-history inspection and modification through the API.Document processed URLs, recipients and business need; declaration alone does not establish actual collection.
bookmarksBookmark creation, organisation and modification.Test mutations and recovery; distinguish business backup from browser permission.
clipboardReadPermission related to clipboard reading through documented mechanisms.Check execution context and gestures required by the chosen API; review copied-data handling.
clipboardWritePermission related to clipboard writing.Observe what is replaced and when; distinguish reading from writing.
nativeMessagingCommunication with a native application registered on the endpoint.Identify the native component, installation, allowed origins, updates and removal.
debuggerDebugging-protocol transport for instrumenting supported targets.Justify the privilege and inspect commands and targets; the name proves neither authorised use nor compromise.
managementInstalled app and extension management; some operations do not require this permission.Map each operation to an API method and administrative need; not every API operation requires this permission.
identityIdentity API, including obtaining OAuth2 access tokens.Separately review OAuth client, scopes, token recipients and revocation; identity does not describe the scopes.
notificationsNotification creation using API mechanisms.Test frequency, sensitive content and interaction; permission does not establish that a notification was actually sent.
unlimitedStorageChanges to applicable storage limits; this is not a host permission.Document volume, retention and purge; do not interpret it as unrestricted access to endpoint files.
webNavigationEvents about navigation progress.Establish which navigations are tracked and transmitted; distinguish navigation events from request modification.

Google Chrome · Permissions · Documentation consulted 2026-10-23; browser behaviour remains version-dependent

Hosts, paths and context: five reference points

Hosts, paths and context: five reference points
Declaration or mechanismUseful interpretationLimit to retain
host_permissions: https://intranet.example.org/private/*A path appears in the pattern but is ignored for host permissions.Do not promise access limited to /private/ from this line alone.
content_scripts.matches + exclude_matchesStatic-script injection conditions combine inclusions and exclusions.Code may also register or inject scripts; this reader does not evaluate these conditions.
*://*.example.org/*The scheme wildcard covers HTTP and HTTPS; this pattern includes the base host and its subdomains.Do not confuse extension patterns with administrative-policy syntax.
<all_urls>Scope over allowed schemes, subject to browser-specific restrictions.The declaration does not show that every page, local file or incognito context is accessible.
activeTab and file:///*activeTab depends on invocation; file URLs require access granted in settings.Test the real context. Neither the manifest nor this reader reveals choices made in the profile.

Google Chrome · Match patterns · Documentation consulted 2026-10-23; browser behaviour remains version-dependent

Google Chrome · activeTab · Documentation consulted 2026-10-23; browser behaviour remains version-dependent

Google Chrome · Content scripts · Documentation consulted 2026-10-23; browser behaviour remains version-dependent

로컬 V3 매니페스트 리더

Paste a Manifest V3 JSON manifest to inventory permissions and site declarations. Processing stays in this page: no installation, site request, local persistence, text transmission or export. Examples are fictional and illustrate result interpretation.

Limited to 64 KiB UTF-8, 200 declarations, 20 content_scripts blocks and 2,048 characters per value. The reader examines four permission lists and static scripts’ matches and exclude_matches. It retains every occurrence with its path. It does not validate pattern syntax, Chrome rules, installation warnings, globs, frames, code files, network rules, OAuth tokens, policies or granted access. Out-of-scope top-level keys are reported without reading their values; JSON accepted here can still be rejected by Chrome. For repeated JSON keys, JSON.parse retains the last value; review the original file to resolve ambiguity.

Eight examples available without JavaScript

Invoked action on a tab
{
    "manifest_version": 3,
    "name": "CIE fictional review example",
    "version": "1.0.0",
    "permissions": [
        "activeTab",
        "scripting",
        "storage"
    ]
}

Three API permissions and no host lists. activeTab may supply temporary access after invocation; inspect the gesture and code. No host list does not prove no access.

Cookies and requests over broad scope
{
    "manifest_version": 3,
    "name": "CIE fictional review example",
    "version": "1.0.0",
    "permissions": [
        "cookies",
        "webRequest"
    ],
    "host_permissions": [
        "<all_urls>"
    ]
}

Two API permissions and one <all_urls> declaration. Review host grants, operations and actual restrictions. webRequest is not synonymous with webRequestBlocking.

Optional capabilities
{
    "manifest_version": 3,
    "name": "CIE fictional review example",
    "version": "1.0.0",
    "permissions": [
        "storage"
    ],
    "optional_permissions": [
        "history"
    ],
    "optional_host_permissions": [
        "https://*/*"
    ]
}

One required permission, one optional permission and one optional host declaration. These are possible requests, not evidence that history and every HTTPS host are already granted.

Static script with an exclusion
{
    "manifest_version": 3,
    "name": "CIE fictional review example",
    "version": "1.0.0",
    "content_scripts": [
        {
            "matches": [
                "https://*.example.org/*"
            ],
            "exclude_matches": [
                "https://private.example.org/*"
            ],
            "js": [
                "content.js"
            ],
            "run_at": "document_idle"
        }
    ]
}

One matches and one exclude_matches in the same block. Both lines are displayed without automatic subtraction. js and run_at are not analysed; effective scope requires code and injection-condition review.

Permission outside the selection and misleading path
{
    "manifest_version": 3,
    "name": "CIE fictional review example",
    "version": "1.0.0",
    "permissions": [
        "alarms"
    ],
    "host_permissions": [
        "https://intranet.example.org/private/*"
    ]
}

alarms is outside this 20-name selection: absence from the directory does not mean Chrome does not recognise it. /private/* in host_permissions does not limit access to that directory.

Identity and native component: visible limits
{
    "manifest_version": 3,
    "name": "CIE fictional review example",
    "version": "1.0.0",
    "permissions": [
        "identity",
        "nativeMessaging"
    ],
    "background": {
        "service_worker": "worker.js"
    },
    "oauth2": {
        "client_id": "fictional.apps.example.invalid",
        "scopes": [
            "fictional-scope"
        ]
    },
    "externally_connectable": {
        "matches": [
            "https://portal.example.org/*"
        ]
    }
}

Two known permissions; background, oauth2 and externally_connectable are reported as out-of-scope top-level keys. The reader establishes nothing about scopes, service-worker code or native correspondents.

Incorrect field type
{
    "manifest_version": 3,
    "name": "CIE fictional review example",
    "version": "1.0.0",
    "permissions": "tabs"
}

permissions must be an array of strings for this reader. No partial result remains when the type is incorrect.

Manifest V2: unsupported reading
{
    "manifest_version": 2,
    "name": "CIE fictional legacy example",
    "version": "1.0.0",
    "permissions": [
        "https://*/*",
        "tabs"
    ]
}

Version 2 is explicitly refused. Its legacy host declarations are not reinterpreted as V3. No browser-compatibility verdict is produced.

Turn reading into a verifiable decision

  1. Fix the purpose and scope

    Record extension identifier, publisher, distribution source, version, browser and test endpoint. Connect each capability to a task and affected data.

  2. Compare requested, granted and observed

    Record manifest declarations, profile access choices and applied policies, then observe gestures and traffic using test data. These three levels are not interchangeable.

  3. Repeat after change

    Compare versions, permissions, hosts, rules and native components. Installation warnings depend on permission combinations; their number is not a security score.

  4. Test restriction and removal

    In managed Edge, a blocked permission can disable an extension without removing it. Check policy scope and separately remove native components and external data where required. Retain evidence of the final state.

Google Chrome · Permission warning guidelines · Documentation consulted 2026-10-23; browser behaviour remains version-dependent

Google Chrome · Stay secure · Documentation consulted 2026-10-23; browser behaviour remains version-dependent

Microsoft Learn · Manage Microsoft Edge extensions using group policies · Enterprise policy documentation consulted 2026-10-23

Technical references: Google Chrome for Developers and Microsoft Learn, linked below and at each permission. Google documentation is CC BY 4.0 except where noted; descriptions and questions above are CIE editorial synthesis adapted into French and English. Fictional examples are original. This page is not a Google or Microsoft validation.

Google Developers · Site policies · Documentation attribution and reuse conditions

Creative Commons Attribution 4.0

Verified documentary source

Chrome permissions · 2026-10-23

Source HTML SHA-256: 0d8d9b108def74b5a47c392b5c9018ed0bf6b3e02a12315a95b31e7e753c5166

공식 참조

참조는 방법을 뒷받침합니다. 상황에 맞게 검사를 조정하십시오. 이는 인증이 아닙니다. 원본 참조 제목 및 소스 문서는 다른 언어로 작성되었을 수 있습니다.

참고 자료 확인일 .