Best practices

​

Environment configuration

​

Environment variables

# Required environment variables
export BMS_DB_USER="your_database_username"
export BMS_DB_PASSWORD="your_secure_password"
export BMS_DB_SERVER="your_database_server"
export BMS_DB_PORT="5432"
export BMS_DB_NAME="postgres"

​

Initial setup

1. Copy the environment template:
   cp .env.example .env
   
2. Configure all required variables with production values
3. Restrict file permissions (Linux/Mac):
   chmod 600 .env
   
4. Verify configuration is not exposed:
   # Ensure .env is in .gitignore
   git check-ignore .env
   

​

Connection string security

public string ProcessConnectionString(string connectionString)
{
    if (string.IsNullOrEmpty(connectionString))
        return connectionString;

    var processed = connectionString;

    foreach (var mapping in _environmentMappings)
    {
        var placeholder = mapping.Key;
        var envVarName = mapping.Value;
        var envValue = Environment.GetEnvironmentVariable(envVarName);

        if (!string.IsNullOrEmpty(envValue))
        {
            processed = processed.Replace(placeholder, envValue);
        }
        else if (processed.Contains(placeholder))
        {
            // Only warn if connection string actually contains placeholders
            Console.WriteLine($"Warning: Environment variable '{envVarName}' not found. Using placeholder value.");
        }
    }

    return processed;
}

​

Database security

​

Connection security

• Enable SSL in your database server configuration
• Use connection strings with SSL mode enabled
• Verify SSL certificates to prevent man-in-the-middle attacks

Server={{DB_SERVER}};Port={{DB_PORT}};Database={{DB_NAME}};User Id={{DB_USER}};Password={{DB_PASSWORD}};SSL Mode=Require;Trust Server Certificate=false;

​

Credential management

• Use passwords at least 16 characters long
• Include uppercase, lowercase, numbers, and symbols
• Avoid dictionary words and common patterns
• Use a password manager to generate and store credentials

• Create dedicated database user for BMS POS application
• Grant only necessary permissions (SELECT, INSERT, UPDATE, DELETE)
• Avoid using superuser accounts for application connections
• Regularly rotate database passwords

​

SQL injection prevention

// Secure parameterized query example
var employee = await _context.Employees
    .FirstOrDefaultAsync(e => e.EmployeeId == request.EmployeeId && e.IsActive);

​

PIN security

​

PIN requirements

• Minimum length: 4 digits
• Recommended length: 6 digits
• Avoid sequential numbers (1234, 5678)
• Avoid repeated digits (1111, 9999)
• Avoid birth dates and other personal information
• Change PINs periodically (every 90 days for managers)

​

BCrypt configuration

private const int WorkFactor = 12; // BCrypt work factor (cost)

• Work factor 12 provides strong security for 2024+
• Higher work factors increase computation time
• Balance security with user experience (login speed)
• Consider increasing work factor as hardware improves

​

Legacy PIN migration

1. Automatic upgrade occurs on first login:
   AuthController.cs:193-204

   if (_pinSecurityService.IsLegacyPin(storedPin))
   {
       // Legacy plaintext comparison
       bool isValid = storedPin == providedPin;
       
       // If valid, upgrade to hashed PIN in background
       if (isValid)
       {
           _ = Task.Run(async () => await UpgradeLegacyPinAsync(storedPin, providedPin));
       }
       
       return isValid;
   }
   
2. Monitor migration progress through audit logs
3. Verify all PINs upgraded before removing legacy support

​

Session management

​

Session storage

• Sessions stored in browser localStorage
• Appropriate for desktop kiosk deployment model
• Relies on physical device security

• localStorage persists across browser restarts
• Data accessible to JavaScript on same origin
• Not suitable for shared or untrusted devices

​

Auto-logout

• Configurable timeout period (default: 15-30 minutes)
• Warn user before logout
• Clear session data on logout
• Require re-authentication to resume

​

Session validation

• Check session token validity
• Verify user still has active account
• Confirm role permissions haven’t changed
• Log suspicious session activity

​

Physical security

​

Device security

• Keep POS terminals in secure, supervised areas
• Lock devices when unattended
• Use cable locks for hardware theft prevention
• Enable BIOS/firmware passwords
• Configure auto-lock on inactivity

• Full disk encryption (BitLocker, LUKS)
• Trusted Platform Module (TPM) for key storage
• Secure boot configuration
• Disable unnecessary USB ports
• Physical intrusion detection

​

Access control

• Limit who can access POS terminals physically
• Supervise training sessions with production systems
• Log all physical access to server rooms
• Use security cameras in POS areas

• Power down or lock terminals when closed
• Store backup devices in locked cabinets
• Implement alarm systems
• Document device inventory regularly

​

Network security

​

Localhost communication

• Backend API binds only to localhost (127.0.0.1)
• Not accessible from network
• Prevents remote attacks
• Suitable for single-device deployment

​

External connections

• Use SSL/TLS for remote database connections
• Configure firewall rules to restrict database access
• Use VPN when accessing cloud databases
• Monitor connection logs for anomalies

​

Backup and recovery

​

Backup strategy

// BMS POS includes SupabaseBackupService for automated backups
// Configure regular backup schedule (daily recommended)

• Automate daily backups
• Store backups on separate device/location
• Encrypt backup files
• Test restoration procedures regularly
• Maintain offsite backup copies
• Document backup and restore procedures

​

Disaster recovery

1. Backup restoration procedures
2. Alternative POS operations (manual fallback)
3. Contact information for support
4. Hardware replacement procedures
5. Data integrity verification steps

​

Audit and monitoring

​

Regular reviews

• Review failed login attempts
• Check for unusual transaction patterns
• Verify system health indicators
• Monitor available disk space

• Generate activity summary reports
• Review user access patterns
• Check for software updates
• Verify backup completion

• Comprehensive security audit
• Review employee access levels
• Update security documentation
• Test disaster recovery procedures

​

Security metrics

• Failed login attempts per day
• Number of role mismatch events
• Average session duration
• Transaction void frequency
• Manager override frequency
• After-hours activity

​

Software updates

​

Update policy

• Apply security patches immediately
• Test in staging environment first
• Schedule downtime during off-hours
• Maintain rollback plan

• Review release notes for security fixes
• Update dependencies monthly
• Test all features after updates
• Document update history

​

Dependency management

# Check for outdated packages
dotnet list package --outdated
npm outdated

# Update dependencies
dotnet restore
npm update

​

Compliance considerations

​

PCI-DSS considerations

• Use PA-DSS validated payment terminals
• Never store full card numbers
• Encrypt cardholder data in transit and at rest
• Implement access control and monitoring
• Conduct regular security assessments
• Maintain PCI compliance documentation

​

Data privacy regulations

• Document what personal data is collected
• Implement data retention policies
• Provide data export capabilities
• Support data deletion requests
• Obtain proper consent for data collection
• Appoint data protection officer if required

​

Financial regulations

• Retain transaction records per legal requirements
• Implement tamper-evident audit logs
• Support tax reporting requirements
• Document internal controls
• Conduct regular financial audits

​

Security roadmap

​

Upcoming features

• Two-factor authentication for Manager accounts
• Biometric authentication support
• Smart card/badge integration
• SSO integration for enterprise deployments

• Enhanced tamper protection
• Cryptographic hash chaining
• External SIEM integration
• Automated anomaly detection

• Database encryption at rest
• End-to-end encryption for sensitive data
• Key management service integration
• Data loss prevention (DLP) features

• Application code signing
• Automated security scanning in CI/CD
• Vulnerability disclosure program
• Security certification compliance

​

Incident response

​

Security incident procedures

1. Contain - Isolate affected systems immediately
2. Assess - Determine scope and impact
3. Document - Preserve evidence and logs
4. Notify - Inform stakeholders and authorities as required
5. Remediate - Fix vulnerabilities and restore systems
6. Review - Conduct post-incident analysis

​

Reporting vulnerabilities

• Description of the vulnerability
• Steps to reproduce
• Potential impact assessment
• Suggested remediation if known
• Your contact information

​

Resources

​

Security references

• OWASP Top 10
• BCrypt Documentation
• PostgreSQL Security
• PCI Security Standards

​

Support

• Review the Security Policy
• Check Audit Logging documentation
• Contact your system administrator
• Report security vulnerabilities privately

​

Next steps