Frequently Asked Questions

KRIOSA AI is an advanced security platform that uses artificial intelligence to protect your applications and data from threats. It provides real-time threat detection, automated responses, and comprehensive security analytics to keep your systems safe.

KRIOSA AI uses machine learning algorithms to analyze traffic patterns, user behavior, and system activities. It identifies anomalies and potential threats in real-time, then takes automated actions to block attacks, notify administrators, and provide detailed forensic data for investigation.

• AI-Powered: Uses machine learning to adapt to new threats
• Real-time Detection: Identifies threats as they happen
• Automated Response: Takes immediate action without human intervention
• Multi-tenant Architecture: Perfect for SaaS platforms
• Comprehensive Analytics: Detailed insights into security events

To create an account:

1. Click the "Get Started" button on the homepage or on the navigation bar
2. Enter your email address and create a password
3. Verify your email address via the confirmation link sent to your inbox
4. Complete your profile information
5. Choose your subscription plan

To reset your password:

1. Click "Forgot Password" on the login page
2. Enter your email address
3. Check your email for a password reset link
4. Click the link and enter your new password
5. Confirm the new password and save changes

You can change your account settings by:

1. Logging into your dashboard
2. Clicking on your profile icon in the top-right corner
3. Selecting "Account Settings" from the dropdown menu
4. Updating your information and clicking "Save Changes"

KRIOSA AI detects a wide range of threats including:

• Brute force attacks
• SQL injection attempts
• Cross-site scripting (XSS)
• DDoS attacks
• Bot traffic
• Anomalous user behavior
• API abuse
• Zero-day exploits

KRIOSA AI's threat detection is highly accurate, with:

• High detection rate for known threats
• 85% accuracy for anomaly detection
• Less than 0.1% false positive rate
• Continuous learning from new threat patterns

Yes, KRIOSA AI supports multiple two-factor authentication methods:

• SMS-based 2FA: Receive codes via text message
• Authenticator apps: Google Authenticator, Microsoft Authenticator
• Hardware keys: YubiKey support
• Biometric: Fingerprint and facial recognition (mobile apps)

We accept the following payment methods:

• Credit/Debit cards (Visa, MasterCard, American Express)
• PayPal
• Bank transfers (for annual plans)
• Cryptocurrency (Bitcoin, Ethereum) for enterprise plans

Yes, you can upgrade or downgrade your plan at any time:

1. Go to "Billing" in your dashboard
2. Click "Change Plan"
3. Select your new plan
4. Confirm the change

Changes take effect immediately, and you'll be prorated for the remainder of your billing cycle.

We offer a 30-day money-back guarantee on all annual plans. Monthly plans can be canceled at any time, but refunds are only provided for the current month if canceled within the first 7 days.

KRIOSA AI integrates with a wide range of services:

1. Go to Integrations page in your dashboard
2. Click "Add Integration" and select "Slack"
3. Enter a name for your integration
4. Paste your Slack webhook URL
5. Click "Test Configuration" to verify
6. Click "Create Integration"

Once configured, KRIOSA AI will send security alerts to your specified Slack channel.

KRIOSA AI requires:

• PHP: 7.4 or higher

You can integrate KRIOSA AI using our REST API:

// Example API call
$response = curl -X POST https://kriosa.com/v2/protect \
  -H "Content-Type: application/json" \
  -H "X-API-Key: your-api-key" \
  -d '{
    "user_id": 123,
    "ip_address": "192.168.1.100",
    "resource": "/api/login"
  }'

We also provide SDKs for:

• PHP
• JavaScript/Node.js
• Python
• Java
• Ruby

KRIOSA AI uses industry-standard encryption:

• In transit: TLS 1.3 for all API communications
• At rest: AES-256 encryption for stored data
• Passwords: bcrypt with salt
• API keys: Encrypted in database, masked in logs

This is the most common issue. Here's how to fix it:

1. Check if the file is in the right place
   Make sure kriosa.php is uploaded to your server. The error "Failed to open stream: No such file or directory" means the file isn't found.
2. Verify the path in your require statement
   Use __DIR__ to build the correct path:

   // If kriosa.php is in the same folder:
   require_once __DIR__ . '/kriosa.php';

   // If kriosa.php is in the root, but you're in a subfolder (like includes/):
   require_once __DIR__ . '/../kriosa.php';

3. Enable error display to see the actual error
   Add these lines at the top of your PHP file:

   error_reporting(E_ALL);
   ini_set('display_errors', 1);

4. Linux servers are case-sensitive
   Make sure the filename case matches: kriosa.php not Kriosa.php
5. Disable the auto-execution
   Add this BEFORE including the file:

   define('KRIOSA_SKIP_AUTO', true);
   require_once __DIR__ . '/kriosa.php';

This means PHP cannot find the kriosa.php file at the path you specified.

• Check that the file exists on your server
• Verify the path is correct (Linux is case-sensitive!)
• Use absolute path or __DIR__ to avoid path issues

Debug tip: Add this to see where you are:

echo "Current directory: " . __DIR__;
echo "Looking for: " . __DIR__ . '/kriosa.php';

This is usually caused by environment differences:

Solutions:

• Use the exact same case as the filename
• Check file permissions: chmod 644 kriosa.php
• Use __DIR__ instead of relative paths

The file is being included, but the class isn't loading properly.

• Make sure the file doesn't have syntax errors: php -l kriosa.php
• Check for BOM (Byte Order Mark) in the file
• Verify the class name spelling: class Kriosa (capital K)

head -c 3 kriosa.php | xxd
# Should show: 3c 3f 70 (<?p) NOT: ef bb bf

Free hosting often restricts outbound cURL requests.

Test if cURL works on your server:

$ch = curl_init('https://kriosa.com/api.php/v1/protect');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$result = curl_exec($ch);
var_dump($result);

If cURL is blocked, use fallback mode:

$kriosa = new Kriosa($apiKey, ['fail_closed' => false]);
// This will allow all requests if API can't be reached

Run these checks to identify the issue: