security-standards

Enforce secure credential handling and authentication practices across software projects.

6|Updated Feb 20, 2025
One-click install
npx skills add https://github.com/zerobias-org/module --skill security-standards-zerobias-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-standards
Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/security-standards
Command: npx skills add https://github.com/zerobias-org/module --skill security-standards-zerobias-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes secure credential handling and authentication practices across modules to prevent secrets leakage and misconfigurations.

Core Features & Use Cases

  • Never commit secrets, credential handling policies, and avoid including credentials in environment configurations.
  • Credential discovery: prioritizes .env, .connectionProfile.json, and prompts for user input when needed.
  • Secure storage and logging: guidelines for storing credentials securely, masking in logs, and using configuration profiles.

Quick Start

Enforce secure credential handling across your module by adopting environment-based storage and strict access controls.

Frequently Asked Questions about security-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent API keys and secrets from being committed to my codebase?

To prevent secrets leakage, enforce credential handling policies that avoid including API keys directly in code and mandate environment-based storage using .env files or connection profiles.

What is the best way to securely store credentials and manage environment configuration?

Secure credential storage is best handled by using .env files or .connectionProfile.json, prioritizing environment-based configuration over hardcoding, and prompting for user input when needed.

How do I mask sensitive credentials in application logs and error handling?

Mask sensitive credentials in logs by applying secure logging guidelines that redact secrets during error handling, ensuring API keys and environment configuration values are never exposed in output.

Can I use this to enforce authentication practices across multiple software modules?

Yes, you can enforce secure authentication and credential handling practices across multiple modules to standardize policies and prevent secrets misconfiguration throughout your software projects.

How does credential discovery work when setting up environment configuration?

Credential discovery works by prioritizing existing .env files and .connectionProfile.json during initialization, then prompting for user input to securely capture any missing secrets or API keys.

Why should I use connection profiles instead of hardcoding secrets in my application?

Using connection profiles prevents secrets leakage by isolating credentials from the codebase, providing strict access controls and standardized storage that hardcoded environment configurations lack.