ILITY Network | Infrastructure Engineering & Security Architecture Update
Dear ILITY Community,
The ILITY Infrastructure and Core Development teams have completed an internal security and asset-related assessment covering the primary service components of the ILITY ecosystem, including blockchain nodes, API gateways, JSON-RPC interfaces, Explorer, Hub, and cross-chain bridge infrastructure.
The assessment examined infrastructure configuration, service dependencies, access control boundaries, asset-related workflows, and operational risk exposure.
Based on our internal findings, we have identified several areas requiring further architectural hardening and more systematic security governance.
Our engineering efforts are currently organized around two primary workstreams: adaptive infrastructure optimization and Zero-Trust-based security architecture.
1. Adaptive Infrastructure & Workload-Aware Resource Management
Workload-responsive resource allocation is currently operational across our node and API server infrastructure.
Our infrastructure team has implemented dynamic resource allocation mechanisms designed to adjust computational capacity in response to changes in user activity, API request volume, and application workloads.
This approach enables more efficient infrastructure utilization compared with relying exclusively on statically provisioned resources.
The current optimization scope includes:
• Workload-Aware Resource Scheduling: Adjusting infrastructure resource allocation according to observed service demand and workload characteristics..
• Compute & Memory Optimization: Refining CPU and memory resource allocation across node and API service environments..
• Service-Level Performance Profiling: Analyzing resource consumption and operational requirements across Explorer, Hub, and supporting backend services..
• Capacity Management: Improving infrastructure readiness for fluctuations in concurrent requests and third-party integration workloads..
• Resource Isolation & Operational Efficiency: Evaluating service-specific resource requirements to reduce unnecessary contention and improve infrastructure utilization..
These improvements are intended to strengthen the operational foundation of ILITY’s application and service layers.
Our focus is on improving infrastructure efficiency while maintaining predictable service behavior as workload requirements evolve.
2. API Architecture Hardening & Structured Request Processing
As blockchain services increasingly depend on API-driven interactions, the security and reliability of their interface layers become critical components of the overall system architecture.
Our development team is conducting architectural improvements across JSON-RPC endpoints, API request processing, and SQL-based data access workflows.
The ongoing engineering scope includes:
JSON-RPC Interface Hardening
Reviewing RPC method exposure, request validation, endpoint access policies, and potential abuse scenarios associated with externally accessible blockchain interfaces.
Structured Query Processing
Refining SQL query handling and database access patterns to improve consistency, reduce unnecessary data exposure, and establish clearer boundaries between application services and persistence layers.
Service-to-Service Communication
Evaluating authentication boundaries, authorization requirements, and access policies governing interactions between internal infrastructure components.
API Security Controls
Reviewing mechanisms such as request throttling, input validation, access logging, and endpoint-level authorization as part of a broader API security improvement program.
These efforts aim to reduce unnecessary attack surfaces and establish more consistent security controls across service interfaces.
3. Zero-Trust Security Architecture
We are progressively developing a Zero-Trust-oriented security model across the ILITY service infrastructure.
The architectural direction follows the principle that access to systems and resources should not be implicitly trusted solely because a request originates from an internal network or previously authenticated environment.
Our current security design work focuses on:
• Identity & Access Management (IAM): Defining clearer authentication and authorization requirements for users, services, and infrastructure operators..
• Principle of Least Privilege (PoLP): Evaluating access permissions to ensure that identities and services receive only the privileges necessary for their intended operations..
• Service Access Segmentation: Reviewing trust boundaries between application components, backend services, and infrastructure management interfaces..
• Policy-Based Access Control: Establishing more structured approaches to evaluating and enforcing access permissions..
• Auditability & Security Observability: Improving the consistency of access records and operational security event visibility..
These controls are being evaluated and introduced progressively, with attention to compatibility, operational requirements, and implementation risk.
The objective is to move toward a security architecture based on explicit authorization, controlled access, and continuous risk assessment.
4. Security Assessment & Infrastructure Risk Management
Our recent internal assessment included a review of systems supporting blockchain interactions, application operations, and digital asset-related processes.
Rather than treating security as an isolated application-layer concern, our approach considers risks across multiple architectural boundaries.
These include:
• External API exposure and request processing.
• Internal service authentication and authorization.
• Database access and query execution.
• Infrastructure configuration and administrative privileges.
• Cross-service dependencies and operational security controls.
The findings are being used to prioritize remediation activities, architectural improvements, and security control implementation.
Our objective is to establish a repeatable security engineering process rather than relying exclusively on individual vulnerability remediation.
This includes improving how security requirements are identified, evaluated, implemented, and reviewed throughout the infrastructure lifecycle.
5. ISO/IEC 27001 Alignment & Security Governance
In parallel with technical infrastructure improvements, we are strengthening our internal information security management practices with reference to ISO/IEC 27001.
Our current direction emphasizes a risk-based approach to security governance, including:
Information Security Risk Assessment
Establishing more structured methods for identifying and evaluating risks associated with infrastructure assets, service operations, and information processing.
Access Control Governance
Reviewing identity management, privileged access, and authorization practices across relevant systems.
Security Operations & Change Management
Improving the consistency of security-related operational procedures and infrastructure change controls.
Audit Readiness & Control Validation
Preparing for more systematic security assessments through documented processes, control reviews, and supporting technical evidence.
These initiatives are intended to support the progressive development of a more mature information security management framework.
ISO/IEC 27001 alignment remains an ongoing effort and should not be interpreted as a claim of certification.
We intend to disclose additional security assessment findings and any independently verified audit or certification outcomes once they become available and are appropriate for public release.
6. Engineering Direction | Operational Resilience by Design
The reliability of a blockchain ecosystem depends not only on its underlying protocol but also on the security and operational characteristics of the services built around it.
Our current infrastructure initiatives therefore focus on three complementary engineering objectives:
• Adaptive Resource Management — Improving infrastructure efficiency through workload-responsive resource allocation and service-specific performance optimization..
• Security Architecture Hardening — Reducing unnecessary exposure across APIs, database interfaces, and internal service communication boundaries..
• Risk-Based Security Governance — Establishing more systematic access controls, operational procedures, and security management practices informed by ISO/IEC 27001..
By addressing these areas together, we aim to strengthen the operational resilience and long-term maintainability of ILITY’s infrastructure.
Our engineering direction is to make infrastructure security, resource efficiency, and operational reliability integral properties of the system architecture rather than isolated improvements.
The ILITY Infrastructure and Development teams will continue implementing and validating these changes, with further technical updates to follow as milestones are completed.
ILITY Foundation | Infrastructure & Core Development Team
Security by Architecture. Efficiency by Design. Resilience by Engineering.
Dear ILITY Community,
The ILITY Infrastructure and Core Development teams have completed an internal security and asset-related assessment covering the primary service components of the ILITY ecosystem, including blockchain nodes, API gateways, JSON-RPC interfaces, Explorer, Hub, and cross-chain bridge infrastructure.
The assessment examined infrastructure configuration, service dependencies, access control boundaries, asset-related workflows, and operational risk exposure.
Based on our internal findings, we have identified several areas requiring further architectural hardening and more systematic security governance.
Our engineering efforts are currently organized around two primary workstreams: adaptive infrastructure optimization and Zero-Trust-based security architecture.
1. Adaptive Infrastructure & Workload-Aware Resource Management
Workload-responsive resource allocation is currently operational across our node and API server infrastructure.
Our infrastructure team has implemented dynamic resource allocation mechanisms designed to adjust computational capacity in response to changes in user activity, API request volume, and application workloads.
This approach enables more efficient infrastructure utilization compared with relying exclusively on statically provisioned resources.
The current optimization scope includes:
• Workload-Aware Resource Scheduling: Adjusting infrastructure resource allocation according to observed service demand and workload characteristics..
• Compute & Memory Optimization: Refining CPU and memory resource allocation across node and API service environments..
• Service-Level Performance Profiling: Analyzing resource consumption and operational requirements across Explorer, Hub, and supporting backend services..
• Capacity Management: Improving infrastructure readiness for fluctuations in concurrent requests and third-party integration workloads..
• Resource Isolation & Operational Efficiency: Evaluating service-specific resource requirements to reduce unnecessary contention and improve infrastructure utilization..
These improvements are intended to strengthen the operational foundation of ILITY’s application and service layers.
Our focus is on improving infrastructure efficiency while maintaining predictable service behavior as workload requirements evolve.
2. API Architecture Hardening & Structured Request Processing
As blockchain services increasingly depend on API-driven interactions, the security and reliability of their interface layers become critical components of the overall system architecture.
Our development team is conducting architectural improvements across JSON-RPC endpoints, API request processing, and SQL-based data access workflows.
The ongoing engineering scope includes:
JSON-RPC Interface Hardening
Reviewing RPC method exposure, request validation, endpoint access policies, and potential abuse scenarios associated with externally accessible blockchain interfaces.
Structured Query Processing
Refining SQL query handling and database access patterns to improve consistency, reduce unnecessary data exposure, and establish clearer boundaries between application services and persistence layers.
Service-to-Service Communication
Evaluating authentication boundaries, authorization requirements, and access policies governing interactions between internal infrastructure components.
API Security Controls
Reviewing mechanisms such as request throttling, input validation, access logging, and endpoint-level authorization as part of a broader API security improvement program.
These efforts aim to reduce unnecessary attack surfaces and establish more consistent security controls across service interfaces.
3. Zero-Trust Security Architecture
We are progressively developing a Zero-Trust-oriented security model across the ILITY service infrastructure.
The architectural direction follows the principle that access to systems and resources should not be implicitly trusted solely because a request originates from an internal network or previously authenticated environment.
Our current security design work focuses on:
• Identity & Access Management (IAM): Defining clearer authentication and authorization requirements for users, services, and infrastructure operators..
• Principle of Least Privilege (PoLP): Evaluating access permissions to ensure that identities and services receive only the privileges necessary for their intended operations..
• Service Access Segmentation: Reviewing trust boundaries between application components, backend services, and infrastructure management interfaces..
• Policy-Based Access Control: Establishing more structured approaches to evaluating and enforcing access permissions..
• Auditability & Security Observability: Improving the consistency of access records and operational security event visibility..
These controls are being evaluated and introduced progressively, with attention to compatibility, operational requirements, and implementation risk.
The objective is to move toward a security architecture based on explicit authorization, controlled access, and continuous risk assessment.
4. Security Assessment & Infrastructure Risk Management
Our recent internal assessment included a review of systems supporting blockchain interactions, application operations, and digital asset-related processes.
Rather than treating security as an isolated application-layer concern, our approach considers risks across multiple architectural boundaries.
These include:
• External API exposure and request processing.
• Internal service authentication and authorization.
• Database access and query execution.
• Infrastructure configuration and administrative privileges.
• Cross-service dependencies and operational security controls.
The findings are being used to prioritize remediation activities, architectural improvements, and security control implementation.
Our objective is to establish a repeatable security engineering process rather than relying exclusively on individual vulnerability remediation.
This includes improving how security requirements are identified, evaluated, implemented, and reviewed throughout the infrastructure lifecycle.
5. ISO/IEC 27001 Alignment & Security Governance
In parallel with technical infrastructure improvements, we are strengthening our internal information security management practices with reference to ISO/IEC 27001.
Our current direction emphasizes a risk-based approach to security governance, including:
Information Security Risk Assessment
Establishing more structured methods for identifying and evaluating risks associated with infrastructure assets, service operations, and information processing.
Access Control Governance
Reviewing identity management, privileged access, and authorization practices across relevant systems.
Security Operations & Change Management
Improving the consistency of security-related operational procedures and infrastructure change controls.
Audit Readiness & Control Validation
Preparing for more systematic security assessments through documented processes, control reviews, and supporting technical evidence.
These initiatives are intended to support the progressive development of a more mature information security management framework.
ISO/IEC 27001 alignment remains an ongoing effort and should not be interpreted as a claim of certification.
We intend to disclose additional security assessment findings and any independently verified audit or certification outcomes once they become available and are appropriate for public release.
6. Engineering Direction | Operational Resilience by Design
The reliability of a blockchain ecosystem depends not only on its underlying protocol but also on the security and operational characteristics of the services built around it.
Our current infrastructure initiatives therefore focus on three complementary engineering objectives:
• Adaptive Resource Management — Improving infrastructure efficiency through workload-responsive resource allocation and service-specific performance optimization..
• Security Architecture Hardening — Reducing unnecessary exposure across APIs, database interfaces, and internal service communication boundaries..
• Risk-Based Security Governance — Establishing more systematic access controls, operational procedures, and security management practices informed by ISO/IEC 27001..
By addressing these areas together, we aim to strengthen the operational resilience and long-term maintainability of ILITY’s infrastructure.
Our engineering direction is to make infrastructure security, resource efficiency, and operational reliability integral properties of the system architecture rather than isolated improvements.
The ILITY Infrastructure and Development teams will continue implementing and validating these changes, with further technical updates to follow as milestones are completed.
ILITY Foundation | Infrastructure & Core Development Team
Security by Architecture. Efficiency by Design. Resilience by Engineering.
