Cuestionario vinculado a una guía · Medio Nivel

Cuestionario sobre firma de modelos y seguridad de la cadena de suministro de ML

Distinga la integridad y procedencia de los artefactos de la calidad del modelo e identifique los riesgos de una serialización no confiable y controles de liberación débiles.

Rutas de guía relacionadasFirma del modelo de seguridad de la cadena de suministro de ML
Pregunta 1 de 8

¿Qué establece más directamente la verificación de una firma digital en un artefacto?

Vista previa de cada pregunta8 preguntas

Las respuestas y explicaciones aparecen a medida que realiza el cuestionario.

  1. ¿Qué establece más directamente la verificación de una firma digital en un artefacto?
    • The bytes match a signature associated with a trusted signing identity
    • The model is accurate on every future dataset
    • The model is free of bias
    • The training data were collected ethically
  2. ¿Por qué es riesgoso cargar un pepinillo Python que no es de confianza?
    • It always deletes the source file
    • Deserialization can execute arbitrary code
    • It cannot represent numeric tensors
    • It guarantees a model will be biased
  3. ¿Qué puede agregar la procedencia de la construcción a un artefacto modelo firmado?
    • A model card describing intended use
    • A vulnerability report listing known component issues
    • Evidence about source, build steps and inputs
    • An evaluation report containing only validation metrics
  4. ¿Por qué la implementación debe exigir la verificación de firmas?
    • Only evaluation reports need verification
    • Signing automatically blocks every unsigned file
    • Verification changes model weights into a safe format
    • A signature provides no protection if deployment accepts artifacts without checking it
  5. ¿Qué no demuestra una firma válida?
    • That the bytes match the signed digest
    • That the signed model is safe or accurate
    • That a trusted identity signed it under policy
    • That the artifact was not altered after signing
  6. Why keep a dependency lockfile and source revision in release provenance?
    • They replace model evaluation
    • They guarantee every package has no vulnerabilities
    • They help trace which inputs produced the deployed artifact
    • They ensure the host driver is installed
  7. How does an SBOM differ from a signature?
    • It describes the build workflow and source revision
    • It verifies artifact bytes against a signing identity
    • It reports model quality on an evaluation set
    • It inventories software components; it answers a different question from integrity verification
  8. Which action protects signing credentials?
    • Limit key access and plan rotation or managed identity use
    • Commit private keys into the model repository
    • Share credentials across all build users
    • Disable verification after signing