Tag: technology

  • Integrating Generative AI in ITSM Workflows

    Integrating Generative AI in ITSM Workflows

    IT Service Management (ITSM) teams are increasingly turning to generative AI (GenAI) to streamline workflows, reduce resolution times, and improve user satisfaction. In this post, we’ll explore two architectures for integrating GenAI into platforms like ServiceNow: man-in-the-middle (human-in-the-loop) and agentic automation (autonomous AI agents).


    Why GenAI for ITSM?

    • Ticket overload: Teams handle hundreds of tickets daily, leading to burnout and delays.
    • Knowledge gaps: Agents struggle to find relevant solutions quickly.
    • Repetitive tasks: Manual triage and updates consume valuable time.

    GenAI can automate classification, suggest solutions, and even resolve incidents-but how you integrate it matters. Let’s compare two approaches.


    Architecture 1: Man-in-the-Middle (Human-in-the-Loop)

    In this approach, GenAI acts as an assistant to human agents. It analyzes tickets, suggests actions, and automates tasks but requires human approval before execution.

    Workflow Diagram:

    Use Cases:

    • High-risk scenarios (e.g., critical infrastructure changes).
    • Compliance-heavy environments (e.g., healthcare, finance).

    Implementation Steps:

    1. Set Up ServiceNow Outbound REST Integration (javascript)

    // ServiceNow Scripted REST API (Outbound)
    var request = new sn_ws.RESTMessageV2();
    request.setEndpoint('https://your-middleware.com/process-ticket');
    request.setHttpMethod('POST');
    request.setRequestBody(JSON.stringify(current));
    var response = request.execute();

    2. Build Middleware (Python/Flask Example)

    from flask import Flask, request, jsonify
    import openai

    app = Flask(__name__)
    openai.api_key = "your-api-key"

    @app.route('/process-ticket', methods=['POST'])
    def handle_ticket():
    ticket_data = request.json

    # GenAI analysis
    prompt = f"""
    Classify this ITSM ticket and suggest priority (Critical/High/Medium/Low):
    Title: {ticket_data['short_description']}
    Description: {ticket_data['description']}
    """

    response = openai.ChatCompletion.create(
    model="gpt-4",
    messages=[{"role": "user", "content": prompt}]
    )

    suggestion = response.choices[0].message['content']
    return jsonify({"suggestion": suggestion, "ticket_id": ticket_data['number']})

    3. Human Review & Action
    Agents review GenAI’s suggestions in a dashboard and approve/reject them.


    Architecture 2: GenAI Agentic Automation

    Here, GenAI agents act autonomously within guardrails. They analyze tickets, execute actions (e.g., resolving incidents, updating KBs), and only escalate exceptions to humans.

    Workflow Diagram:

    Use Cases:

    • Low-risk, repetitive tasks (e.g., password resets, FAQ responses).
    • High-volume environments needing 24/7 support.

    Implementation Steps:

    1. Autonomous Ticket Resolution with Python

    import requests
    import openai

    def resolve_ticket_automatically(ticket_id):
    # Fetch ticket from ServiceNow
    snow_url = f"https://instance.service-now.com/api/now/table/incident/{ticket_id}"
    headers = {"Accept": "application/json"}
    auth = ("admin", "password")
    response = requests.get(snow_url, headers=headers, auth=auth)
    ticket = response.json()['result']

    # GenAI analysis
    prompt = f"""
    Resolve this ticket autonomously if possible. Provide a solution and mark as closed.
    Ticket: {ticket['description']}
    """

    ai_response = openai.ChatCompletion.create(
    model="gpt-4",
    messages=[{"role": "user", "content": prompt}]
    )

    # Auto-resolve if confidence is high
    if "reset password" in ai_response.choices[0].message['content'].lower():
    update_data = {
    "state": "6", # Resolved
    "close_notes": "Automatically resolved: Password reset instructions sent."
    }
    requests.patch(snow_url, json=update_data, headers=headers, auth=auth)

    2. Guardrails for Safety

    • Limit permissions (e.g., agents can’t modify user roles).
    • Log all actions for auditing.
    • Escalate tickets containing keywords like “outage” or “data breach” to humans.

    Key Considerations

    Combined Architecture Diagram:


    Best Practices for Both Architectures

    • Data Privacy: Mask PII/PHI in tickets before sending to GenAI APIs.
    • Feedback Loops: Let agents rate AI suggestions to improve models.
    • Tooling: Use frameworks like LangChain for complex workflows.

    Conclusion

    Whether you choose man-in-the-middle or agentic automation depends on your risk tolerance and use case. Start with a hybrid approach: use autonomous agents for simple tasks (e.g., FAQs) and human-in-the-loop for critical workflows. As trust in the system grows, expand automation cautiously.

    GenAI is set to redefine ITSM, propelling organizations from automation to true intelligence. The journey is just beginning-those who embrace this shift will not only optimize IT operations but also unlock new levels of agility, resilience, and innovation. The future of ITSM is not just faster or cheaper-it’s smarter, more adaptive, and profoundly more human.

  • Infrastructure as Code (IaC) Security Best Practices

    Infrastructure as Code (IaC) Security Best Practices

    Infrastructure as Code (IaC) has revolutionized how we provision and manage infrastructure, enabling speed, repeatability, and scalability. However, as with any code, IaC introduces new security considerations. Misconfigurations, exposed secrets, and lack of visibility can lead to significant risks in production environments.

    This guide explores actionable best practices for securing your Terraform, Ansible, and other IaC pipelines-helping you build robust, compliant, and resilient infrastructure. Sample code and how-to notes included!


    1. Treat IaC Like Application Code

    Just as you would with application code, store your IaC in version control systems (e.g., Git). This enables:

    • Change tracking: Who changed what, when, and why.
    • Peer reviews: Enforce code reviews and approvals before merging.
    • Rollback: Revert to previous known-good states if issues arise.

    Tip:
    Use branch protection rules and require pull request reviews for all changes.


    2. Secrets Management

    Never hard-code secrets or sensitive data (API keys, passwords, certificates) in your IaC files. Instead:

    • Use secret management tools like HashiCorp Vault, AWS Secrets Manager, or Azure Key Vault.
    • Integrate secrets into your pipelines at runtime, not in code.
    • Leverage environment variables or encrypted files for sensitive values.

    Sample: Fetching Secrets from Vault in Terraform

    provider "vault" {
      address = "https://vault.example.com"
    }
    
    resource "vault_generic_secret" "example" {
      path = "secret/data/myapp"
    }
    
    output "db_password" {
      value = vault_generic_secret.example.data["password"]
    }

    How-to:

    • Replace https://vault.example.com with your Vault server address.
    • The vault_generic_secret resource fetches secrets dynamically.
    • Output blocks can reference secrets securely-never hardcode them!

    Sample: Encrypting Secrets in Ansible with ansible-vault

    - hosts: all
      vars_files:
        - secrets.yml
      tasks:
        - name: Use secret password
          debug:
            msg: "The password is {{ secret_password }}"

    How-to:

    • Create and encrypt the secrets file: ansible-vault create secrets.yml
    • Reference the encrypted file in your playbook under vars_files.
    • Access secrets in tasks using Jinja2 templating, e.g., {{ secret_password }}.

    3. Automated Security Scanning

    Integrate security tools into your CI/CD pipeline to catch misconfigurations and vulnerabilities early:

    Sample: Terraform Security Scanning with tfsec in GitHub Actions

    name: Terraform Security Scan
    
    on: [push]
    
    jobs:
      tfsec:
        runs-on: ubuntu-latest
        steps:
          - uses: actions/checkout@v2
          - name: Run tfsec
            uses: aquasecurity/tfsec-action@v1
            with:
              tfsec_version: 'latest'

    How-to:

    • Add this workflow to your .github/workflows directory.
    • The scan will fail the build if critical security issues are found, helping you catch problems early.

    4. Principle of Least Privilege

    Ensure that your IaC tools, pipelines, and the resources they provision follow the principle of least privilege:

    • Limit IAM permissions for automation accounts.
    • Avoid using overly broad roles or root accounts.
    • Regularly audit permissions and remove unnecessary access.

    5. Policy as Code

    Define and enforce security and compliance policies programmatically:

    • Use tools like Open Policy Agent (OPA), Sentinel (for Terraform Cloud), or Conftest.
    • Enforce rules such as “no public S3 buckets,” “encryption enabled,” or “no hardcoded credentials.”

    Example:
    OPA policies can block deployments that violate security standards before they reach production.


    6. Continuous Monitoring and Drift Detection

    Even after deployment, infrastructure can drift from the desired state:

    • Use tools like Terraform Cloud, AWS Config, or Driftctl to detect and remediate drift.
    • Set up alerts for unauthorized changes and automate remediation where possible.

    7. Regular Reviews and Updates

    IaC modules and dependencies evolve-so should your security practices:

    • Schedule regular reviews of your IaC codebase and third-party modules.
    • Update modules to patch vulnerabilities and leverage new security features.
    • Document your security practices and train your team.

    Conclusion

    Securing Infrastructure as Code is not a one-time task, but a continuous process woven into your development and deployment lifecycle. By treating IaC like application code, managing secrets securely, automating scanning, enforcing least privilege, and using policy as code, you can drastically reduce risk and build trust in your automation.

  • How to Benchmark Enterprise Storage: Fio and Vdbench Explained

    How to Benchmark Enterprise Storage: Fio and Vdbench Explained

    Enterprise storage arrays from vendors like Dell EMC, NetApp, and Pure Storage are the foundation of mission-critical IT environments. Ensuring these systems deliver consistent, high performance under real-world workloads is essential for application reliability and business continuity. In this post, we’ll explore how to benchmark enterprise storage using two industry-leading tools- Fio and Vdbench– with practical configuration examples and best practices.

    Why Benchmarking Enterprise Storage is Unique

    Enterprise arrays are not just fast disks-they’re complex systems with:

    • Multiple controllers and cache layers
    • Advanced data protection (RAID, erasure coding)
    • High-speed protocols (Fibre Channel, iSCSI, NVMe-oF)
    • Storage tiering and virtualization
    • Multi-protocol (block, file) support

    Benchmarking these systems is different from testing a single SSD or HDD. You must simulate production-like workloads, test at scale, and observe performance under both normal and failure conditions.

    Best Practices for Enterprise Storage Benchmarking

    • Simulate real-world workloads: Use realistic mixes of random/sequential I/O, read/write ratios, and block sizes.
    • Test at scale: Ensure test data sets exceed cache sizes and run with sufficient concurrency.
    • Run long-duration tests: Observe steady-state performance, not just short-term cache hits.
    • Monitor the full stack: Track storage, network, and server metrics.
    • Document everything: Record hardware/software versions, configurations, and test parameters.
    • Include failure scenarios: Simulate controller or network failures to test resilience.

    Fio: Flexible I/O Tester

    Fio is a versatile, scriptable tool ideal for generating a wide range of I/O workloads against enterprise storage.

    Example Fio Job File for Enterprise Storage
    text[global]
    ioengine=libaio
    direct=1
    rw=randrw
    rwmixread=70
    bs=8k
    iodepth=64
    numjobs=8
    size=100G
    runtime=3600
    time_based
    group_reporting
    filename=/dev/sdx # Replace with your LUN or device

    [verify]
    verify=crc32

    What this does:

    • Simulates a 70% read/30% write random workload with 8KB blocks.
    • Runs 8 parallel jobs with a queue depth of 64 for 1 hour.
    • Uses direct I/O to bypass the OS cache.
    • Verifies data integrity with CRC32.

    Run it with:

    sudo fio enterprise_test.fio

    Tips:

    • Use multiple devices or files to simulate multi-volume workloads.
    • Adjust concurrency (numjobs, iodepth) to match your environment.
    • Use --output-format=json for detailed reporting.

    Vdbench: Enterprise Workload Generator

    Vdbench is designed for complex, multi-host enterprise storage validation and offers granular workload definition and data validation.

    Example Vdbench Configuration
    text# Storage Definitions for multiple LUNs
    sd=sd1,lun=/dev/sdb,size=100g,openflags=o_direct
    sd=sd2,lun=/dev/sdc,size=100g,openflags=o_direct
    sd=sd3,lun=/dev/sdd,size=100g,openflags=o_direct
    sd=sd4,lun=/dev/sde,size=100g,openflags=o_direct

    # Workload Definition: 67% read, 33% write, 8KB random
    wd=wd1,sd=(sd1-sd4),xfersize=8k,rdpct=67,seekpct=100

    # Run Definition: max I/O, 24 hours, 1s reporting
    rd=rd1,wd=wd1,iorate=max,elapsed=86400,interval=1

    Run it with:

    vdbench -f enterprise_vdbench.conf

    Advanced tips:

    • Use the hd section to define multiple hosts for distributed testing.
    • Simulate failures (e.g., disconnect a path or controller) during the run to observe failover behavior.
    • Use fsd and fwd for NAS/file workloads.

    Key Steps for Success

    1. Profile your workload: Know your application’s I/O patterns. (capture the workload IO pattern)
    2. Prepare your environment: Use dedicated test LUNs/volumes.
    3. Configure your tools: Use Fio or Vdbench job files that match your workload.
    4. Run and monitor: Capture storage, host, and network metrics.
    5. Analyze results: Look for steady-state performance, latency spikes, and the impact of failures.
    6. Document and repeat: Ensure tests are reproducible and results are transparent.

    Conclusion

    Benchmarking enterprise-class storage is about more than just peak numbers-it’s about understanding how your array performs under pressure, during failures, and with your real workloads. Tools like Fio and Vdbench provide the flexibility, power, and validation features needed for accurate, actionable results. By following best practices and using realistic configurations, you can ensure your storage infrastructure is ready for the demands of the modern enterprise.

    References:

    • SNIA Storage Performance Testing Guide
    • Fio and Vdbench Official Documentation
  • The EU AI Act: A New Framework for the Development and Use of Artificial Intelligence

    The EU AI Act: A New Framework for the Development and Use of Artificial Intelligence

    The European Union has introduced a new framework for the development and use of Artificial Intelligence (AI). The AI Act  which The European Parliament passed the AI Act on June 14, 2023., aims to ensure that AI is developed and used in a way that respects fundamental rights and freedoms, such as the right to privacy, the right to non-discrimination, and the right to safety.

    The AI Act identifies three categories of AI systems:

    • High-risk AI systems: These systems are considered to pose a high risk to fundamental rights and freedoms. High-risk AI systems will be subject to strict requirements, such as mandatory ex-ante conformity assessments, transparency obligations, and user control mechanisms.
    • Moderate-risk AI systems: These systems are considered to pose a moderate risk to fundamental rights and freedoms. Moderate-risk AI systems will be subject to a lighter set of requirements than high-risk AI systems, such as risk management measures and transparency obligations.
    • Low-risk AI systems: These systems are considered to pose a low risk to fundamental rights and freedoms. Low-risk AI systems will not be subject to any specific requirements under the Act.

    The AI Act also establishes a new European Artificial Intelligence Board (EAAB) to oversee the implementation of the Act. The EAAB will be composed of representatives from the European Commission, national authorities, and stakeholders.

    The AI Act is a significant piece of legislation that will have a major impact on the development and use of AI in the European Union. The Act is still under negotiation, but it is expected to be finalized in 2023.

    Here are some of the key benefits of the EU AI Act:

    • Ensure that AI is developed and used in a way that respects fundamental rights and freedoms. The EU high-risk AI regulation will ban AI systems that are considered to pose an unacceptable risk to fundamental rights and freedoms. This includes AI systems that are used for social scoring, mass surveillance, or biometric identification without consent. The regulation will also require AI systems that are considered to pose a high risk to fundamental rights and freedoms to comply with a number of safeguards. These safeguards will help to ensure that AI systems are developed and used in a way that respects the fundamental rights and freedoms of individuals.
    • Create a level playing field for businesses that develop and use AI in the European Union. This is because the regulation will apply to all AI systems that are considered to pose a high risk, regardless of where the developer or user is located. This will help to prevent businesses from moving their operations to countries with less stringent AI regulations in order to avoid compliance costs. The regulation will also require businesses to comply with a number of technical standards, which will help to ensure that AI systems are interoperable and that data can be shared more easily between different systems. This will make it easier for businesses to develop and use AI solutions, and it will also help to boost innovation in the field of AI.
    • Help to boost innovation in the field of AI. The AI Act regulations are designed to boost innovation in the field of AI by providing a clear framework for the development and use of AI systems. The regulation will also create a level playing field for businesses, which will make it easier for them to invest in AI research and development.

    Here are some of the potential challenges of the EU AI Act:

    • It could be difficult to implement and enforce.
    • It could stifle innovation in the field of AI.
    • It could lead to the fragmentation of the AI market in the European Union.

    Overall, the EU AI Act is a positive step towards ensuring that AI is developed and used in a responsible and ethical way. However, it is important to be aware of the potential challenges of the Act and to work to mitigate them.

    To learn more about the EU AI Act, please visit the following link: https://artificialintelligenceact.eu/

  • AI Infrastructure 101: Getting started with scalable AI

    AI Infrastructure 101: Getting started with scalable AI

    Artificial Intelligence (AI) has revolutionized businesses, streamlining and optimizing operations while increasing efficiency and productivity. However, companies often face challenges in the implementation and management of AI; this could either be a failure to identify the appropriate use cases for AI or guaranteed functionality and efficiency.

    AI adoption calls for a comprehensive understanding of its lifecycle, and companies need to make sure they focus on three critical areas – Silicon, Software, and Services.

    In this blog post, we’ll delve into these areas, their importance, and their relevance in the AI Lifecycle.

    Silicon: Silicon-based chips, are a foundational material in modern AI infrastructure. It comprises traditional components such as the central processing unit (CPU), the graphics processing unit (GPU), memory, network, and data storage. A scalable and resilient AI infrastructure creates a solid foundation for enterprise deployment, capable of supporting complex algorithms, data storage, and analysis. A robust infrastructure facilitates the acceleration of the AI process, enabling businesses to handle large amounts of data and process information in real-time. Therefore, reliable modern infrastructure components are essential for AI success.

    The use of modern AI infrastructure also allows for optimal performance. Modern silicon-based processors are specifically designed for tasks such as machine learning and intensive data processing. They offer high computational power, increased energy efficiency, and real-time parallelism capabilities. This combination of performance and efficiency ensures the smooth operation of AI applications, providing users with fast and accurate results.

    Furthermore, it plays a crucial role in the data storage and transmission of data required for AI. Modern data infrastructure enables quick access to large data sets making sure processing cycles are not wasted. Additionally, modern networking facilitates fast and reliable data transfer between different components of the AI infrastructure.

    Silicon is the essential element of modern AI infrastructure. With its high performance, energy efficiency, and data storage and transmission capabilities, silicon enables businesses to successfully deploy advanced AI solutions.

    Software: The software layer is equally as important as the hardware layer and is a critical component of the overall AI ecosystem. The software layer encompasses a wide range of AI algorithms that support the general AI infrastructure to achieve business outcomes.

    These AI ecosystem can vary from simple “no-code” tools that allow users to manage AI operations and pipelines, to “Super User” tools that assist users in building and operating flexible and precise AI models. These tools are vital in identifying the necessary AI use cases and implementing optimal solutions. In your AI journey, there must be a recognition of different types of software to streamline AI operations, manage costs, and ensure maximum efficiency. By understanding the software layer of AI, businesses can establish a solid foundation to harness the full potential of this groundbreaking technology.

    AI software ecosystem is dynamic and evolving rapidly. Below is the AI software market glance from IDC’s point of view.

    Services: Services play a critical role in the AI ecosystem. The tools and software utilized in the AI lifecycle are still new and evolving, which is why services are crucial to ensuring smooth integration and efficient operation. Services have so far been ignored by most businesses, but as AI operations become more complex, businesses need to incorporate them into their operations to avoid operational challenges. The services layer includes workforce preparedness to scale and support AI operations, operationalizing data management and analytics workloads, and delivering workload automation.

    Understanding the AI lifecycle is critical for implementing and maintaining AI solutions successfully; companies should prioritize and focus on the Silicon, Software, and Services layers. It is crucial to have a reliable infrastructure regardless of the hardware used and to implement software tools that correlate with the AI problems faced to ensure smooth operations. Finally, businesses must recognize the pivotal role played by the services layer and adequately plan for its integration into their AI ecosystem.

    In summary, businesses that identify the appropriate use cases for AI and implement optimal solutions will reap numerous benefits and gain a competitive edge in today’s fast-paced technological environment. Here are my 3 suggestions to increase changes in your AI pilot

    • Incorporate Real-World Business Use Case
    • Develop a Technology Infrastructure and Integrate AI as a tenant
    • Bring AI to your data