What are security best practices for managing custom inputs in Morpheus? (Select two.)

Question

Options

• AEnforcing static values for all cloud configurations
• BImplementing input validation to prevent incorrect values
• CDisabling API-based access for all custom inputs
• DUsing encrypted fields for credentials and sensitive data

• A
  18% (3)
• B
  76% (13)
• C
  6% (1)

Explanation

Input validation (B) and encrypted fields for sensitive data (D) are the two security pillars for custom inputs in Morpheus. Validation ensures users can only submit acceptable values, preventing misconfigurations or injection attacks. Encrypted fields protect credentials and secrets at rest, so sensitive data is never exposed in plaintext within the platform.

Why the distractors fail:

• A is wrong because static values eliminate the flexibility that custom inputs are designed to provide - the goal is to control dynamic values, not eliminate them.
• C is wrong because disabling API access would break legitimate automation workflows; the right approach is securing API access, not removing it.

Memory tip: Think "Validate what goes IN, Encrypt what's sensitive" - V and E map to B and D. If an option suggests removing functionality entirely (static values, no API), it's almost always a distractor in security questions.

No community discussion yet for this question.