الموارد · 19

مراجعة إضافات المتصفح قبل نشرها على مستوى المؤسسة.

تقييم الأذونات، والوصول إلى المواقع، والتحديثات، وإمكانية إزالة الإضافة.

مُحدَّث · 9 min

محطة خيالية لمراجعة وصول الإضافات دون أشخاص، شاشة ببطاقات أذونات تجريدية وروابط مواقع ومكتب أسود وإضاءة ذهبية رسم توضيحي تحريري مولّد بالذكاء الاصطناعي

ما يُساعد هذا الدليل على تحقيقه

  • جرد الإضافات.
  • تحديد الأذونات.
  • التحكم في التحديثات.
  • تجهيز الإزالة.

فحص سريع

  • ما المهمة المحددة التي تتطلب الإضافة؟
  • ما المواقع والبيانات التي يمكنها الوصول إليها؟
  • هل الأذونات متناسبة؟
  • من يراقب الإصدارات الجديدة؟
  • كيف يمكن تعطيلها على جميع نقاط النهاية المتأثرة؟

طريقة خطوة بخطوة

  1. 1

    جرد الاستخدام

    جمع الإضافات المثبتة، والمعرفات، والإصدارات، والمتصفحات، والمستخدمين، والفرق، والمالكين. البحث عن الإضافات المكررة والإضافات التي ليس لها مالك مسؤول.

    المُخرَج: سجل مُؤرَّخ للإضافات والملكية.

  2. 2

    تحديد الحاجة

    ربط كل إضافة بمهمة حقيقية والبدائل المتاحة. تحديد البيانات والمواقع المعنية قبل تقييم أذوناتها.

    المُخرَج: موجز الاستخدام والنطاق.

  3. 3

    مراجعة الوصول

    قراءة بيان الأذونات وتحذيرات الأذونات للوصول إلى المضيف، وعلامات التبويب، والتخزين، والحافظة، والقدرات الأخرى المطلوبة. التمييز بين الأذونات الأساسية والاختيارية.

    المُخرَج: جدول أذونات مُبرَّر أو قابل للتخفيض.

  4. 4

    التحقق من الناشر والتغييرات

    توثيق الناشر، ومصدر التوزيع، وسياسة الخصوصية، وتغييرات الإصدار. لا يُغني وجود التطبيق في المتجر عن هذه المراجعة.

    المُخرَج: سجل المصدر وآلية إعادة التقييم.

  5. 5

    النشر مع الضوابط

    اختبار الإضافة في ملف تعريف مناسب ببيانات ملائمة، ثم تحديد قائمة معتمدة أو قواعد حظر للمتصفح المُدار.

    المُخرَج: القرار، وإعدادات النشر، والمسؤول.

  6. 6

    التخطيط للخروج

    تجهيز التعطيل السريع، والإزالة، وتحديد نقاط النهاية المتأثرة، والتعامل مع البيانات التي قد تكون مُعرَّضة للخطر أثناء وقوع حادث.

    المُخرَج: إجراء إزالة مُختَبَر.

افهم واحسب واتخذ القرار

صلاحيات الإضافات: القدرة والنطاق والتفعيل

في Chrome Manifest V3، عدد الصلاحيات ليس مقياساً للأمن. افصل قدرة الواجهة البرمجية والمواقع المشمولة ولحظة منح الوصول.

تمنح activeTab وصولاً مؤقتاً بعد إجراء صريح من المستخدم. قد يستمر عند التنقل داخل الأصل نفسه؛ ويُسحب عند تغيير الأصل أو إغلاق علامة التبويب. تبقى صفحات المتصفح المقيدة مستثناة.

المؤشرات والأدلة

المؤشرالتفسيرالدليل المطلوب
activeTab وصول مؤقت بعد استدعاء المستخدم فحص الإجراء وسحب الوصول عند تغيير الأصل
scripting قدرة على حقن برنامج نصي يلزم أيضاً وصول للصفحة عبر صلاحية المضيف أو activeTab
content_scripts.matches أنماط المواقع لبرامج المحتوى النصية فحصها إضافة إلى permissions وhost_permissions

مؤشرات الإدارة

المؤشرما يقيسهالإجراء الأول
التغطيةإضافات ذات مالك وغرض موثقينحل مشكلة التثبيتات بدون مالك
الوصول المبررالأذونات المرتبطة بالوظائف المطلوبةتقليل أو رفض الوصول المفرط
مراجعة التغييراتتقييم إصدارات Material قبل النشر على نطاق واسعإيقاف تحديث محفوف بالمخاطر مؤقتًا
اختبار الإزالةنقاط النهاية المشمولة باختبار التعطيلإصلاح ثغرات النشر والاستثناءات

الأخطاء الشائعة

  • اعتبار إدراج المتجر بمثابة موافقة أمنية
  • قبول الوصول إلى كل موقع بدون سبب
  • الإضافات المفقودة في الملفات الشخصية
  • عدم مراجعة الأذونات بعد التحديثات

الأسئلة المتكررة

هل الإضافة الشائعة آمنة؟

لا تحدد الشعبية الأذونات التي يتطلبها استخدامك، أو البيانات التي يمكنه الوصول إليها، أو كيفية تغييرها.

هل يجب حظر كل إضافة؟

تُقيّم السياسة المتناسبة الحاجة، وإمكانية الوصول، وسياق المتصفح المُدار.

متى يجب إعادة التقييم؟

بعد تغييرات في أذونات الوصول، أو الملكية، أو الوظيفة، أو الإصدار، وأثناء المراجعات الدورية للأجهزة.

الإضافات: الأذونات والوصول

الملاحظات المرجعية المفصّلة متاحة باللغة الإنجليزية في هذه النسخة.

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

المراجع الرسمية

تدعم المراجع الطريقة. قم بتكييف عمليات التحقق مع سياقك؛ فهي ليست شهادة. قد تكون عناوين المراجع الأصلية والوثائق المصدرية بلغة أخرى.

تاريخ مراجعة المراجع .