security

🔒 Security Enforcement - ZERO TOLERANCE

Security is as critical as Platform 3.0 compliance. Apply these rules to EVERY app.

🔴 CRITICAL: Input Validation & Command Injection Prevention

All SMI functions MUST validate input. Use allowlists for operations.

Safe Patterns - ALWAYS USE:

// ✅ SAFE - Allowlisted operations only
const ALLOWED_OPERATIONS = ['status', 'list', 'health'];

exports = {
  performOperation: async function(args) {
    if (!ALLOWED_OPERATIONS.includes(args.operation)) {
      return { success: false, error: 'Operation not allowed' };
    }
    // Execute only pre-defined, safe operations
    return await executeAllowedOperation(args.operation);
  }
};

// ✅ SAFE - Parameterized operations with validation
exports = {
  getData: async function(args) {
    const id = parseInt(args.id, 10);
    if (isNaN(id) || id < 0) {
      return { success: false, error: 'Invalid ID' };
    }
    // Use validated input
    return await fetchDataById(id);
  }
};

// ✅ SAFE - String sanitization
function sanitizeInput(str) {
  if (typeof str !== 'string') return '';
  return str.replace(/[<>\"\'&]/g, '');
}

Input Validation Checklist:

• Validate all input types (string, number, boolean)
• Sanitize strings (remove/escape special characters)
• Use allowlists for enumerated values
• Reject unexpected or malformed input
• Never trust client-provided data

---

🟠 HIGH: Logging Security - No Sensitive Data

Log only operation status and non-sensitive identifiers.

Safe Logging Patterns:

// ✅ SAFE - Log only confirmation, no sensitive data
onAppInstallHandler: function() {
  console.log('App installed successfully');
}

// ✅ SAFE - Log only non-sensitive, specific fields
onTicketCreateHandler: function(args) {
  console.log('Ticket created:', args.data?.ticket?.id);
}

// ✅ SAFE - Sanitized error logging
try {
  await performOperation();
} catch (e) {
  console.error('Operation failed:', e.message);
}