Recursos · 19
Revisar las extensiones del navegador antes de la implementación empresarial
Evaluar permisos, acceso al sitio, actualizaciones y capacidad de eliminar una extensión.
Actualizado · 9 min
Lo que esta guía ayuda a lograr
- Ampliaciones de inventario
- Calificar permisos
- Actualizaciones de controles
- Preparar eliminación
Comprobación rápida
- ¿Qué tarea específica requiere la extensión?
- ¿A qué sitios y datos puede acceder?
- ¿Son proporcionados los permisos?
- ¿Quién ve las nuevas versiones?
- ¿Cómo se puede desactivar en cada endpoint afectado?
Método paso a paso
- 1
Uso de inventario
Recopilar extensiones instaladas, identificadores, versiones, navegadores, usuarios, equipos y propietarios. Encuentre duplicados y extensiones sin un propietario responsable.
Entregable: extensión fechada y registro de propiedad.
- 2
Definir la necesidad
Conecta cada extensión a una tarea real y alternativas disponibles. Defina los datos y los sitios involucrados antes de juzgar sus permisos.
Entregable: resumen de uso y alcance.
- 3
Acceso a revisión
Leer el manifiesto y las advertencias de permisos para acceso al host, pestañas, almacenamiento, portapapeles y otras capacidades solicitadas. Distinguir la situación de los permisos opcionales.
Entregable: grilla de permisos justificados o reducibles.
- 4
Consultar editor y cambios
Documente el editor, la fuente de distribución, la política de privacidad y los cambios de versión. La presencia en la tienda por sí sola no reemplaza esta revisión.
Entregable: registro de procedencia y disparador de reevaluación.
- 5
Implementar con controles
Pruebe la extensión en un perfil apropiado con datos adecuados, luego establezca una lista aprobada o reglas de bloqueo para el navegador administrado.
Entregable: decisión, configuración de implementación y propietario.
- 6
Planificar la salida
Preparar rápidamente la desactivación, eliminación, identificación de endpoints afectados y manejo de datos potencialmente expuestos durante un incidente.
Entregable: procedimiento de remoción probado.
Comprender, calcular y decidir
Permisos de extensiones: capacidad, alcance y activación
En Chrome Manifest V3, el número de permisos no es una puntuación de seguridad. Separe lo que permite la API, los sitios afectados y el momento en que se concede acceso.
activeTab concede acceso temporal tras una acción explícita. Puede mantenerse al navegar dentro del mismo origen; se revoca al cambiar de origen o cerrar la pestaña. Las páginas restringidas del navegador siguen excluidas.
Indicadores y pruebas
| Indicador | Interpretación | Prueba necesaria |
|---|---|---|
| activeTab | Acceso temporal tras invocación del usuario | Comprobar gesto y revocación al cambiar de origen |
| scripting | Capacidad de inyectar un script | Requiere además acceso a la página, por host o activeTab |
| content_scripts.matches | Patrones de sitios para scripts de contenido | Revisarlos además de permissions y host_permissions |
Indicadores de gestión
| Indicador | Qué mide | Primera acción |
|---|---|---|
| Cobertura | Extensiones con propietario y finalidad documentados | Resolver instalaciones sin propietario |
| Acceso justificado | Permisos vinculados a funciones requeridas | Reducir o rechazar el acceso excesivo |
| Cambios revisados | Versiones de materiales evaluadas antes de su implementación generalizada | Pausar una actualización riesgosa |
| Eliminación probada | Endpoints cubiertos por una prueba de inhabilitación | Solucionar lagunas y excepciones en la implementación |
Errores comunes
- Tratar la ficha de Play Store como una aprobación de seguridad
- Aceptar acceso a todos los sitios sin motivo
- Faltan extensiones en perfiles personales
- No se pueden revisar los permisos después de las actualizaciones
Preguntas frecuentes
¿Es segura una extensión popular?
Popularidad no establece qué permisos requiere su uso, a qué datos puede acceder o cómo puede cambiar.
¿Se deben prohibir todas las extensiones?
Una política proporcionada evalúa la necesidad, el acceso y el contexto del navegador gestionado.
¿Cuándo se debe reevaluar?
Después de cambios de permiso material, propiedad, función o versión y durante revisiones periódicas de la flota.
Extensiones: permisos y acceso
Las notas detalladas de esta edición están disponibles en inglés.
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
| Manifest field | What it declares | CIE review question |
|---|---|---|
| permissions | Required API permissions. | Which function justifies each capability? No warning does not mean no access. |
| optional_permissions | API permissions requestable at runtime, subject to API restrictions. | Which permissions were actually granted, and can the optional feature be removed? |
| host_permissions | Host 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_permissions | Scope within which host access can be requested at runtime. | Declared scope is not a list of sites already authorised. |
| content_scripts.matches | Patterns 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
Google Chrome · Permissions · Documentation consulted 2026-10-23; browser behaviour remains version-dependent
Hosts, paths and context: five reference points
| Declaration or mechanism | Useful interpretation | Limit 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_matches | Static-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
Lector local de manifiesto 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.
Permisos de API declarados
| Location | Declared permission | Documentary reference |
|---|
Declaraciones de sitios
| Location | Declared value | Reading aid |
|---|
Claves fuera de alcance
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
- 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.
- 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.
- Repeat after change
Compare versions, permissions, hosts, rules and native components. Installation warnings depend on permission combinations; their number is not a security score.
- 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
Referencias oficiales
Las referencias respaldan el método. Adapte los controles a su contexto; no constituyen certificación. Los títulos de referencia originales y los documentos fuente pueden estar en otro idioma.
Referencias consultadas el .
- Chrome Extensions — declaring permissions
- Microsoft Edge — extension management policies
- Google Chrome · Permissions
- Google Chrome · Permissions API
- Google Chrome · activeTab
- Google Chrome · Match patterns
- Google Chrome · Content scripts
- Google Chrome · Permission warning guidelines
- Google Chrome · Stay secure
- Google Developers · Site policies
