ios-security▌
dpearson2699/swift-ios-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Secure iOS apps with Keychain, CryptoKit, biometric authentication, and Apple security best practices.
- ›Covers Keychain Services for credential storage, Data Protection file classes, and CryptoKit for encryption, hashing, and HMAC operations
- ›Includes Secure Enclave key storage, biometric authentication with LocalAuthentication (Face ID/Touch ID), and LAContext configuration
- ›Enforces App Transport Security (ATS) requirements, certificate pinning patterns, and explains kSecAttrAccessibl
iOS Security
Guidance for handling sensitive data, authenticating users, encrypting correctly, and following Apple's security best practices on iOS.
Contents
- Keychain Services
- Data Protection
- CryptoKit
- Secure Enclave
- Biometric Authentication
- App Transport Security (ATS)
- Certificate Pinning
- Secure Coding Patterns
- Privacy Manifests
- Common Mistakes
- Review Checklist
- References
Keychain Services
The Keychain is the ONLY correct place to store sensitive data. Never store passwords, tokens, API keys, or secrets in UserDefaults, files, or Core Data.
Storing Credentials
func saveToKeychain(account: String, data: Data, service: String) throws {
let query: [String: Any] = [
kSecClass as String: kSecClassGenericPassword,
kSecAttrAccount as String: account,
kSecAttrService as String: service,
kSecValueData as String: data,
kSecAttrAccessible as String: kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly
]
let status = SecItemAdd(query as CFDictionary, nil)
if status == errSecDuplicateItem {
let updateQuery: [String: Any] = [
kSecClass as String: kSecClassGenericPassword,
kSecAttrAccount as String: account,
kSecAttrService as String: service
]
let updates: [String: Any] = [kSecValueData as String: data]
let updateStatus = SecItemUpdate(updateQuery as CFDictionary, updates as CFDictionary)
guard updateStatus == errSecSuccess else {
throw KeychainError.updateFailed(updateStatus)
}
} else if status != errSecSuccess {
throw KeychainError.saveFailed(status)
}
}
Reading Credentials
func readFromKeychain(account: String, service: String) throws -> Data {
let query: [String: Any] = [
kSecClass as String: kSecClassGenericPassword,
kSecAttrAccount as String: account,
kSecAttrService as String: service,
kSecReturnData as String: true,
kSecMatchLimit as String: kSecMatchLimitOne
]
var result: AnyObject?
let status = SecItemCopyMatching(query as CFDictionary, &result)
guard status == errSecSuccess, let data = result as? Data else {
throw KeychainError.readFailed(status)
}
return data
}
Deleting Credentials
func deleteFromKeychain(account: String, service: String) throws {
let query: [String: Any] = [
kSecClass as String: kSecClassGenericPassword,
kSecAttrAccount as String: account,
kSecAttrService as String: service
]
let status = SecItemDelete(query as CFDictionary)
guard status == errSecSuccess || status == errSecItemNotFound else {
throw KeychainError.deleteFailed(status)
}
}
kSecAttrAccessible Values
| Value | When Available | Device-Only | Use For |
|---|---|---|---|
kSecAttrAccessibleWhenUnlocked |
Device unlocked | No | General credentials |
kSecAttrAccessibleWhenUnlockedThisDeviceOnly |
Device unlocked | Yes | Sensitive credentials |
kSecAttrAccessibleAfterFirstUnlock |
After first unlock | No | Background-accessible tokens |
kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly |
After first unlock | Yes | Background tokens, no backup |
kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly |
Passcode set + unlocked | Yes | Highest security |
Rules:
- Use
ThisDeviceOnlyvariants for sensitive data. Prevents backup/restore to other devices. - Use
AfterFirstUnlockfor tokens needed by background operations. - Use
WhenPasscodeSetThisDeviceOnlyfor most sensitive data. Item is deleted if passcode is removed. - NEVER use
kSecAttrAccessibleAlways(deprecated and insecure).
Keychain Access Groups
Share keychain items across apps from the same team:
let query: [String: Any] = [
kSecClass as String: kSecClassGenericPassword,
kSecAttrAccount as String: "shared-token",
kSecAttrAccessGroup as String: "TEAMID.com.company.shared"
]
@AppStorage vs Keychain
| Storage | Use For | Security |
|---|---|---|
@AppStorage / UserDefaults |
Non-sensitive preferences (theme, onboarding state, feature flags) | Not encrypted at rest |
| Keychain | Passwords, tokens, API keys, secrets | Hardware-encrypted, access-controlled |
Rule: If the data would be embarrassing or dangerous if exposed, it goes in Keychain. Everything else can use @AppStorage.
// Non-sensitive preference -- @AppStorage is fine
@AppStorage("hasCompletedOnboarding") private var hasOnboarded = false
// Sensitive credential -- MUST use Keychain
// WRONG: @AppStorage("authToken") private var token = ""
// CORRECT: Use saveToKeychain(account:data:service:)
Data Protection
iOS encrypts files based on their protection class:
| Class | When Available | Use For |
|---|---|---|
.complete |
Only when unlocked | Sensitive user data |
.completeUnlessOpen |
Open handles survive lock | Active downloads, recordings |
.completeUntilFirstUserAuthentication |
After first unlock (default) | Most app data |
.none |
Always | Non-sensitive, system-needed data |
// Set file protection
try data.write(to: url, options: .completeFileProtection)
// Check protection level
let attributes = try FileManager.default.attributesOfItem(atPath: path)
let protection = attributes[.protectionKey] as? FileProtectionType
Use .complete for any file containing user-sensitive data. The default
.completeUntilFirstUserAuthentication is acceptable for general app data.
CryptoKit
Use CryptoKit for all cryptographic operations. Do not use CommonCrypto or the raw Security framework for new code.
Symmetric Encryption (AES-GCM)
import CryptoKit
let key = SymmetricKey(size: .bits256)
func How to use ios-security on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add ios-security
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches ios-security from GitHub repository dpearson2699/swift-ios-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate ios-security. Access the skill through slash commands (e.g., /ios-security) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★56 reviews- ★★★★★Ren Perez· Dec 16, 2024
ios-security reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Zara Menon· Dec 16, 2024
Registry listing for ios-security matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ira Jain· Dec 12, 2024
ios-security fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Diya Verma· Nov 11, 2024
ios-security has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Neel Anderson· Nov 7, 2024
Registry listing for ios-security matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Omar Verma· Nov 7, 2024
ios-security reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kofi Jackson· Nov 3, 2024
ios-security fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kofi White· Oct 26, 2024
Keeps context tight: ios-security is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Isabella Patel· Oct 26, 2024
I recommend ios-security for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Neel Thomas· Oct 22, 2024
ios-security is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 56