Skip to main content
View all solutions
Security/Certification

ISMS (Information Security Management)

Comprehensively manages policy establishment, control implementation, and security audits to protect critical corporate information and data assets.

ISO/IEC 27001 (Information Security Management)
01

Are you facing these challenges?

1. There is no dedicated security officer, and IT staff handle security as an additional duty

In most cases, the person who manages servers and networks also takes on information security work. Account issuance, permission changes, backup checks, and filling out prime contractor security checklists all fall on one person. Security policy documents remain as the files prepared for the certification audit, and they have drifted little by little from the actual system settings. When the person in charge changes, no one is left who knows which settings are configured the way they are, or why.

2. You may believe the plant network is safe because it is separated

On the design drawings, the office network and the equipment network are divided, but in practice they connect through several paths. Equipment vendor engineers connect maintenance laptops directly to PLCs, and program backups travel on USB drives. Access paths opened temporarily for remote support sometimes remain in place. Equipment designed on the premise of physical separation (air gap) usually has weak authentication and is difficult to update firmware on, so once the perimeter is breached there is effectively no means of defense.

3. There is no way to confirm where drawings and recipes have gone

Mold drawings, formulation recipes, process conditions, and price lists are core company assets, yet they often sit in shared folders on a file server. Because no record is left of who viewed or downloaded which file and when, there is no basis for proof even when you suspect a departing employee took materials with them. The scope of what was shared while exchanging quotations and drawings with partner companies is likewise not left as a record.

4. Prime contractor security checklists get thicker every year

Supply chain security checklist items from large corporate customers keep increasing, and recently some are requiring ISMS-P certification or equivalent control evidence. Once you receive a checklist, simply requesting and collecting account lists, permission grant histories, log retention policies, and vulnerability remediation records from each server and each responsible person takes weeks. When the same request arrives the following year, you gather everything again from the beginning.

5. One ransomware incident stops the line

In 2017, a single piece of malware paralyzed production and shipping at global manufacturing and logistics companies for several weeks; in 2022, a Japanese automaker halted operations at all of its domestic plants for a day because of a ransomware infection at a parts supplier. Security incidents in manufacturing do not end with information leakage; they lead directly to lost revenue and delivery delays. Yet many companies have no defined procedure for who decides what, and how far to isolate, when an incident occurs.


02

Here is how we solve it

Place controls inside the operational system rather than in documents

Most failures of an information security management system begin where the documents and the reality diverge. Instead of managing security policies as separate documents, VEXPLOR ISMS pushes policies down as access control rules that determine how the actual operational screens behave. When you change a policy, the system behaves differently from that moment on, which reduces the room for documents and settings to drift apart.

  • Security policies are defined in 5 types (access control, authentication, data protection, network, input validation), with specific allow and deny rules placed under each policy.
  • Rules support role-based (RBAC) and attribute-based (ABAC) approaches together. A role rule such as "the quality team may view inspection data" and an attribute condition such as "cost data may be viewed only from internal IP addresses during business hours" can be applied at the same time.
  • When segregation of duties (SoD) rules are registered, the system blocks the same person from serving as both the purchase requester and the acceptance inspector.
  • Revision histories of policies and rules are automatically retained in the audit log, so you can confirm when and by whom a control was relaxed.

A record of who viewed what, and when, is kept automatically

Audit evidence cannot be created after an incident has occurred. The audit log in VEXPLOR ISMS is designed as an append-only structure that cannot be modified or deleted. Activities such as logins, permission changes, data lookups, bulk downloads, and configuration changes are recorded together with the target, action, severity, source IP, and timestamp.

  • Data access logs record, at the item level, which user viewed, created, modified, or deleted which record in which table. For sensitive data such as drawings, recipes, and prices, the system can be configured to leave a record even for a simple lookup.
  • Logs are stored in monthly partitions, and retention periods are managed by type. You can configure them to match legal requirements, such as audit logs for 5 years, personal information access records for 3 years, and login histories for 1 year, and logs past their retention period are moved to archival storage.
  • Hash chaining can be applied for log integrity, allowing you to verify whether records were altered after the fact.

Practical scenario: If an employee scheduled to leave has viewed drawing files far more often than usual over the past 30 days, you can confirm the items involved, the timestamps, and the source IP addresses directly from the data access log. Such records serve as supporting evidence when contesting a trade secret infringement.

Manage plant equipment in a single asset inventory

Information security begins with asset identification, but asset inventories at manufacturing companies usually stop at servers and PCs. VEXPLOR ISMS manages 8 types of OT assets (PLC, SCADA, HMI, DCS, RTU, sensors, network equipment, historians) in a separate inventory and links them to the equipment master.

  • For each asset, the manufacturer, model, firmware version, IP address, physical location, and criticality (low, medium, high, critical) are recorded.
  • You designate which level of the Purdue model each asset belongs to. Assets are divided into 5 zones: field (Level 0), control (Level 1), supervisory (Level 2), manufacturing operations (Level 3), and the buffer zone between IT and OT (DMZ).
  • Because the vulnerability count and the most recent inspection date are managed per asset, equipment that is highly critical but has not been inspected for a long time surfaces as a priority.
  • Assets whose last inspection date exceeds a defined interval trigger automatic alerts, and firmware version changes are recorded in the audit log.

Control partner companies and external access with individual accounts and expiry dates

If you issue shared accounts to equipment vendors and maintenance partners, you cannot determine accountability when an incident occurs. External personnel are issued individual accounts as well, and operations proceed by designating an access scope and a validity period.

  • The account lifecycle is linked to HR information. Permissions are granted by role upon hiring, and when a termination is processed, sessions end immediately and permissions are revoked.
  • Multi-factor authentication (MFA) can be made mandatory for remote access. 3 authentication methods are supported (authenticator app TOTP, SMS, email), and the number of remaining backup codes is tracked.
  • By specifying access time windows, source IP ranges, and target equipment as conditions, you can restrict access so that "engineers from Company A may access only the equipment on a designated line on designated dates."
  • Quarterly access review targets are compiled automatically. Accounts that have gone unused for a long time and excessively granted permissions are presented as a list, so the review task ends with a review and an approval.

Respond in a defined sequence when an incident occurs

Incident response should never require looking up a procedure at the moment a decision is needed. The security incident response procedure is composed as a predefined workflow, so the responsible person and the records carry through each stage from detection to classification, containment, analysis, recovery, and post-incident review.

  • Incident severity is classified into 4 levels. Ransomware, data breaches, and equipment compromise are placed at the highest level, while brute force attempts and port scans are placed at lower levels, varying the intensity of the response.
  • If you set target times by severity level (detection, classification, containment, recovery, reporting), the actual elapsed times are tallied automatically and become the basis for drills and post-incident reviews.
  • For containment, IP blocking, forced session termination, and account lockout are executed directly from the system. When repeated authentication failures or abnormal call volumes are detected, automatic blocking rules act first.
  • If you record the attack tactic and technique classification (MITRE ATT&CK) and indicators of compromise together with the incident, they help in determining whether similar incidents are recurring.

Practical scenario: If login failures repeat from a particular IP address at night, rate limiting blocks the requests first, and once the threshold is exceeded that IP is automatically blocked for 1 hour. A security alert is raised and an incident record is created at the same time, so the next morning the responsible person begins the response by reviewing a timeline that has already been assembled.

Collect certification audit evidence continuously

The burden of certification preparation comes less from maintaining the controls than from gathering the materials that show they were maintained. The compliance check function lets you register the control items of a certification standard and link the corresponding system data to each item as evidence.

  • Multiple standards can be managed in parallel, including ISMS-P, ISO/IEC 27001, and personal information protection requirements, and a single piece of system data is linked simultaneously as evidence for several standards.
  • For items that can be verified in the system, such as account management, access rights review, log retention, and encryption key management, evidence is populated automatically. Evidence that lives outside the system, such as training completion records or physical security inspection photographs, is supplemented with attachments.
  • Because conforming, nonconforming, and not-yet-checked statuses are managed per item, you can identify what is missing and address it before the audit.
  • Whether certification is granted is a matter for the certification body to judge. This function does not guarantee certification; its purpose is to reduce the time spent gathering evidence and performing self-assessments.

03

Global standards this solution follows

Information security standards are not technical specifications; they are international agreement on what must be controlled and to what extent. The requirements of the standards below are reflected in the system architecture, so evidence accumulates through daily operations regardless of which certification you are preparing for.

ISO/IEC 27001:2022 -- The international standard for information security management systems

Why does this standard matter?

ISO/IEC 27001 is the international standard for information security management systems, and it is the most widely recognized in overseas customer audits and in joining global supply chains. In the 2022 revision, the controls in Annex A were consolidated into 93 and reorganized into 4 areas: 37 organizational controls, 8 people controls, 14 physical controls, and 34 technological controls. 11 controls were newly added, including threat intelligence, data leakage prevention, monitoring activities, and information deletion. Specific implementation guidance for the controls is provided in ISO/IEC 27002:2022, which was revised alongside it.

How is it applied in VEXPLOR?

Annex A ControlWhat it means for your operationsVEXPLOR approach
A.5.9 Inventory of information and other associated assetsYou must identify every asset that requires protectionIntegrated management of IT and OT asset inventories, criticality classification
A.5.15 Access controlAccess must be allowed only to the extent the work requiresPolicy-based access control rules, combined role-based and attribute-based application
A.5.18 Access rightsGranted permissions must be reviewed and revoked periodicallyAccount lifecycle management, automatic extraction of quarterly access review targets
A.5.19 Information security in supplier relationshipsAccess granted to partner companies must be controlledIndividual accounts for external parties, designated validity periods and access scopes
A.5.24~A.5.28 Information security incident managementIncident response procedures must be defined in advance and evidence collectedIncident response workflow, target times by severity level, indicator of compromise records
A.8.2 Privileged access rightsAdministrator privileges must be controlled separatelyPrivileged account separation, enforcement of segregation of duties rules
A.8.8 Management of technical vulnerabilitiesVulnerabilities must be assessed and remediated periodicallyVulnerability assessment registration, remediation status tracking, alerts for unremediated items
A.8.15 Logging / A.8.16 Monitoring activitiesActivity records must be kept and anomalies monitoredImmutable audit logs, data access logs, security alerts
A.8.22 Segregation of networksNetworks must be separated by purposePurdue model-based zone definition, allowed communication rules per zone
A.8.24 Use of cryptographyCryptographic algorithms and keys must be managedEncryption key lifecycle management, rotation history tracking, expiry alerts

K-ISMS-P -- Domestic certification and prime contractor requirements

Why does this standard matter?

K-ISMS-P (Korea's Information Security & Personal Information Protection Management System certification) is the criteria applied domestically. The ISMS certification criteria comprise 80 items, being 16 items for establishing and operating the management system plus 64 protection measure requirements; adding 21 requirements covering each stage of personal information processing gives the 101 items of the ISMS-P certification criteria. Most manufacturing companies are not legally obligated to obtain it, but an increasing number of prime contractor supply chain security assessments, public tenders, and investment reviews apply these criteria as a reference requirement.

How is it applied in VEXPLOR?

Certification CriterionWhat it means for your operationsVEXPLOR approach
2.3 External party securityAccess by partner company personnel must be controlled together with the contractSeparate management of external party accounts, automatic deactivation on expiry
2.5.1 User account managementProcedures for requesting, issuing, changing, and deleting accounts must existAccount lifecycle workflow, HR information integration
2.5.5 Special account and privilege managementAdministrator accounts must be minimized and managed separatelyPrivileged account identification, separate tracking of usage history
2.5.6 Access rights reviewGranted permissions must be checked periodicallyReview cycle configuration, automatic listing of unused accounts and excessive permissions
2.6.1 Network accessNetworks must be separated and access controlledIP allow and block lists, communication rules by zone
2.6.6 Remote access controlRemote access must be approved and recordedMandatory multi-factor authentication, time window and IP range restrictions, session records
2.7.2 Encryption key managementProcedures for key generation, use, and destruction must existKey alias, purpose, status, and expiry date management, rotation chain tracking
2.9.4 Log and access record managementRecords must be retained without forgery or alterationAppend-only log structure, automatic retention period management by type
2.11.3 Anomalous behavior analysis and monitoringAbnormal behavior must be detected and addressedLogin failure trends, bulk lookup detection, security alert generation
2.11.5 Incident response and recoveryIncident response procedures and records must existStage-by-stage records for incident registration, containment, recovery, and post-incident review

IEC 62443 -- Industrial control system security

Why does this standard matter?

IEC 62443 is a family of standards addressing the security of industrial automation and control systems. Office IT standards cannot be applied to a plant as they are, because availability of equipment takes precedence over confidentiality and because a reboot or a patch means a production stoppage. This standard divides equipment into zones and conduits, sets the security level (SL 1~4) required for each zone, and then applies controls that match that level.

How is it applied in VEXPLOR?

IEC 62443 Requirement AreaWhat it means for your operationsVEXPLOR approach
Asset identification and classification (62443-2-1)All control assets must be inventoried and assigned a criticalityOT asset inventory with 8 asset types, 4 criticality levels
Zone and conduit design (62443-3-2)Equipment must be divided into zones and boundaries definedAsset placement by Purdue level, definition of allowed protocols between zones
Identification and authentication control (FR1)The identity of anyone accessing equipment must be verifiedAccount-based access, multi-factor authentication for remote maintenance
Use control (FR2)Only authorized work may be performedAccess control rules that designate the target equipment and the scope of work
Restricted data flow (FR5)Communication between zones must be permitted only to the minimum extentRule management that denies by default and allows only the necessary communication
Timely response to events (FR6)Anomalies must be detected and recordedRecords of unauthorized access attempts, security alerts, automatic IP blocking
Patch and change managementPatches for control equipment must be applied after verificationPatch management register, patch deployment workflow (verification, approval, deployment, rollback)

NIST CSF 2.0 -- A maturity benchmark for reporting to executives

Why does this standard matter?

The Cybersecurity Framework of the U.S. National Institute of Standards and Technology added GOVERN in the 2.0 revision of 2024, giving it 6 functions including identify, protect, detect, respond, and recover. It is not a certification scheme but a tool for diagnosing your current level and setting targets, which makes it useful when explaining security investment to executives.

How is it applied in VEXPLOR?

CSF FunctionWhat it means for your operationsVEXPLOR approach
GOVERNSecurity policies and lines of accountability must be establishedRegistration, revision, and approval history management for security policies
IDENTIFYAssets and risks must be understoodIntegrated IT and OT asset inventory, vulnerability status
PROTECTAccess must be restricted and data protectedAccess control rules, multi-factor authentication, encryption key management
DETECTAnomalies must be detectedAudit log analysis, security alerts, rate limiting
RESPONDIncidents must be handled and reportedIncident response workflow, target times by severity level
RECOVERNormal operations must be restored and improvements madeRecovery action records, post-incident review and recurrence prevention registration

04

How it differs from existing systems

Controls inside the operational system, not a document management tool

General information security management tools focus on organizing policy documents and evidence files. Whether the controls are actually observed remains a separate question, and once the audit is over the gap between the documents and the reality widens again. VEXPLOR ISMS operates on the same platform that hosts ERP, MES, and QMS, so an access control rule is the behavior of the operational screen, and the audit log is the audit evidence. No separate evidence production work is required.

A dual-role administrator can define it directly

In a structure where you ask the software vendor to change the permission model and the approval lines and then wait several weeks, controls cannot keep up with reality. Roles, permissions, and approval lines are defined on screen without writing code and applied immediately. In situations where the permission structure changes, such as an organizational restructuring or the start-up of a new line, the administrator can apply it within the same day.

IT and OT viewed in a single inventory

If IT staff manage office network assets while equipment staff manage plant network assets, the boundary zone remains a blind spot. Servers and endpoints are managed in the same asset inventory as PLCs and SCADA systems, linked to the equipment master so you can confirm which equipment corresponds to which asset. Vulnerability assessment results and firmware change histories are kept in the same record system.

Evidence accumulates through daily work rather than after-the-fact collection

Gathering materials just before a certification audit or a prime contractor assessment consumes more of an administrator's time than anything else. Because records are left at the moment accounts are issued, permissions are changed, users log in, data is viewed, and incidents are handled, the assessment can instead be handled by specifying a period and the items and running a query. The same records are linked as evidence for both ISO/IEC 27001 and ISMS-P.


05

How does it compare to global solutions?

Information security tools differ in character. Management tools that organize documents and evidence, monitoring tools that collect logs to detect threats, and the approach of embedding controls in the operational system itself have different purposes, so it is more accurate to see them as a division of roles than as a ranking. The table below summarizes the differences in approach.

Comparison CriterionDocument and spreadsheet-based preparationDomestic GRC management solutionsGlobal GRC platformsDedicated security monitoring (SIEM) toolsVEXPLOR ISMS
Location of controlsDescribed in documentsDocuments and checklist itemsDocuments and risk registerLog collection layerInside the operational system
Evidence collectionManual collection before the auditRegistered by the administratorRegistered by the administratorAutomatic log collectionRecorded automatically as work is performed
Reflection in access rightsNot reflectedRequires separate system configurationRequires integration setupNot reflectedRule changes apply immediately
OT asset managementSeparate listMostly not includedExtension modulePartially supportedLinked to the equipment master
Monitoring and detectionNoneMostly not includedSeparate tool integrationSpecialist domainSIEM, EDR, DLP, and threat intelligence built in
Implementation difficultyLowModerateHighHighProceeds together with the operational system rollout
Dedicated staffing assumptionFeasible as an additional dutyFeasible as an additional dutyAssumes a dedicated organizationAssumes monitoring staffDesigned around dual-role administrators

If management functions and monitoring functions are adopted as separate products, the asset inventory and the incident records split into two sets. The table below summarizes how far each feature area is connected within a single system.

Feature AreaDomestic GRC management solutionsGlobal GRC platformsDedicated security monitoring (SIEM) toolsVEXPLOR ISMSWhat this means for you
Certification criteria item managementExcellentTop-tierNot supportedExcellentMultiple standards managed in parallel with shared evidence
Automatic evidence collectionBasicBasicExcellentExcellentOperational data becomes evidence as it is
Access control enforcementNot supportedBasicNot supportedExcellentPolicy changes carry straight through to screen behavior
Audit trailBasicExcellentTop-tierExcellentImmutable structure and item-level access records
Log correlation analysis (SIEM)Not supportedBasicTop-tierExcellentLog source registration, correlation rules, and alert linkage provided natively
Endpoint protection and response (EDR)Not supportedNot supportedBasicExcellentEndpoint baselines, detection, and response actions connect to incident records
Data loss prevention (DLP)Not supportedNot supportedBasicExcellentLeakage policies and violations connect through to disciplinary and reporting procedures
External threat intelligence integrationNot supportedBasicTop-tierExcellentThreat feed, indicator, and hunting query management
Incident response proceduresBasicExcellentExcellentExcellentResponsible personnel and records at each stage connected as a workflow
OT asset and zone managementNot supportedBasicBasicExcellentPurdue zones and the equipment master managed together
Privileged access management (PAM)Not supportedBasicNot supportedExcellentAdministrator access sessions recorded separately
Security training recordsBasicExcellentNot supportedExcellentTraining courses and completion records connect to audit evidence

Areas where VEXPLOR ISMS is relatively stronger: The management functions (certification criteria, evidence, access review) and the monitoring functions (SIEM, EDR, DLP, threat intelligence) operate on one asset inventory and one incident register. An item detected by the monitoring functions becomes the incident record itself, and that incident record in turn becomes evidence for the certification audit. If two products are adopted separately, this connection has to be built as an integration project. Added to this are access control enforcement inside the operational system, item-level data access records, integrated management of IT and OT assets, and the definition of permissions and approval lines without writing code.

Points you should also review: The antivirus and anti-malware engine itself, network firewall and intrusion prevention appliances, and long-term storage infrastructure for large log volumes are outside the scope of this solution. Leave the security appliances and antivirus software you already use in place, and configure the system to register their detection results as log sources, connecting them to incident response and evidence. If you require response at the level of a monitoring team staffed 24 hours a day, running a specialist managed monitoring service in parallel is the more suitable arrangement.


06

Expected benefits after implementation

Reduced burden of certification and assessment preparation

  • Because evidence that can be verified in the system, such as accounts, permissions, logs, and encryption keys, accumulates continuously, preparation for audits and prime contractor assessments can proceed as a verification task rather than a data-gathering exercise.
  • A single record is linked as evidence for multiple standards, so preparation work does not grow proportionally as the number of certification criteria increases.

Consistency in incident response

  • Detection, classification, containment, recovery, and post-incident review proceed in a fixed sequence, which reduces situations where the level of response varies with the experience of the person on duty.
  • Because the time taken to respond is tallied automatically, procedures can be improved on the basis of drill results.

Deterrence and after-the-fact tracing of insider leakage

  • The simple fact that lookups of sensitive data such as drawings, recipes, and prices are recorded creates a preventive effect.
  • When an incident is suspected, you can confirm who viewed what and when, which provides a basis for establishing the facts and for legal action.

Visibility into OT assets

  • Because a list is maintained of which control devices are in the plant, how many there are, and what firmware version they run, you can immediately grasp the scope of impact when a vulnerability advisory is published.
  • The gap between the target security level and the current state becomes visible, which helps in setting priorities for equipment investment plans.

Operational continuity for dual-role administrators

  • Because policies and rules are recorded in the system, the content of the controls and the reasons for changes carry over even when the person in charge changes.
  • Periodic review targets and items nearing expiry are presented automatically, reducing work that used to depend on memory and personal schedules.

07

Feature guide by operational area

Access control and account management

Access control rules are placed under security policies, and allow or deny decisions are made by matching resource types against roles. Rules are evaluated on a priority basis and use role-based and attribute-based conditions together. Accounts are managed through a lifecycle from issuance to change, dormancy, and disposal, and linked to HR information. Authentication supports 3 multi-factor methods and backup codes, and sessions provide concurrent session limits, inactivity timeouts, and forced termination. Minimum password length and complexity, session duration, allowed login failure counts, and lockout duration are set at the organization level.

Audit trails and data protection

Audit logs record the action, target, severity, source IP, and timestamp together, and prevent forgery and alteration through an append-only structure. Data access logs record lookups, creations, modifications, and deletions at the table and record level. Both logs are stored in monthly partitions and migrated automatically according to retention periods by type. Encryption keys are managed by algorithm (AES-256, RSA-2048, RSA-4096, ECDSA-P256) and by purpose (data encryption, token signing, communication encryption, key exchange), with status and expiry dates tracked; the actual key values are held in a key management system and only the metadata is tracked. When a key is rotated, a reference to the previous key remains so the history can be followed.

Threat detection and incident response

Security alerts are managed by occurrence, acknowledgement, and remediation status. Vulnerability assessments are registered as either scheduled or urgent, and the number of findings, their distribution by severity, and the remediation status are tracked. Security incidents are recorded stage by stage from registration through investigation, response, and closure, with containment and recovery actions and lessons learned retained. 4 operations-center status screens (security incident status, access management, vulnerability status, security audit) are provided and used for continuous monitoring.

Network and OT security

The IP block list supports blocking of both individual addresses and address ranges, and manages manual blocks, automatic blocks, and expiry times separately. Request rate limiting is configured across 6 scopes (global, authentication, AI, code generation, upload, real-time communication), and authentication-related requests are limited strictly to defend against brute force attacks. The OT asset inventory manages type, manufacturer, model, firmware, IP, level, and criticality, and tracks the vulnerability count and the most recent inspection date alongside them.

Integrated log analysis and threat intelligence (SIEM)

Logs from multiple sources such as firewalls, servers, and operational systems are registered and gathered in one place, and correlation rules group individual events into a single threat. For example, when events that look harmless on their own, such as "repeated authentication failures late at night followed by a success and then a bulk lookup," match a rule, a correlation alert is generated and, depending on severity, automatically converted into an incident record. By registering external threat intelligence feeds you can manage known malicious IP addresses, domains, and hashes as indicators, and by saving hunting queries you can repeatedly search past logs for traces when a new threat is disclosed.

Endpoint protection and leakage prevention (EDR, DLP)

The installation status and last communication time of the agent installed on each endpoint are managed, and a normal baseline is registered per endpoint so that behavior outside it is detected. Response actions such as quarantine and process blocking are retained as records against each detection. Leakage prevention is managed through policies by channel. Policies are applied to paths through which materials can leave, such as email attachments, web uploads, external storage devices, and printing, and when a violation occurs it is handled through warning, blocking, and reporting stages, connecting through to HR disciplinary procedures where necessary. If drawings and recipes are registered in the sensitive data list, the handling of those materials is tracked separately.

Privileged accounts and single sign-on (PAM, SSO)

Sessions accessed with administrator privileges are recorded separately from ordinary access. Because a record is left of who used a privileged account, when, and for what purpose, you obtain the administrator access control evidence that prime contractor assessments frequently request. Service accounts used for system-to-system integration rather than by people are also managed as a separate list, allowing you to find integration accounts that have been left in place without an expiry. Through single sign-on (SSO) configuration, the system can be connected to your existing internal account infrastructure.

Vulnerability remediation and security training

Vulnerability assessment results are managed per finding, with detailed descriptions, severity, and remediation status. When remediation requires a patch, it is registered in the patch management register and proceeds as a workflow through verification, approval, deployment, and rollback stages. Because patching production equipment entails a stoppage, this verification stage is especially important. Security training registers courses and manages completion records by employee. Evidence of training delivery, required in certification audits and prime contractor assessments, accumulates automatically.

Compliance checks and evidence management

Check items are registered by standard, and conforming, nonconforming, and not-yet-checked statuses are managed together with the evidence. Items that can be verified in the system have evidence linked automatically, and evidence outside the system is supplemented with attachments. Nonconforming items are assigned corrective actions, responsible personnel, and deadlines, and completion is tracked. If a schedule for periodic checks is registered, an alert is raised when it comes due.



08

Solutions that work well together

SolutionIntegration Details
GroupwareEmployee accounts, organization charts, and approval lines shared as the basis for permission management; security policy announcements and training record management
HRAccount creation, permission changes, and revocation applied automatically at hiring, transfer, and departure
PLMViewing history and export control for drawings and specifications, access grade management for development assets
MESProduction equipment and control terminals incorporated into the asset inventory, access zone control for shop floor accounts
EAMEquipment master shared as the basis for the OT asset inventory, security patch and inspection history management
ERPItem-level access records for sensitive data such as customers, prices, and costs

09

Suitable companies

  • Parts and materials companies subject to prime contractor supply chain security assessments: Companies that must respond to large corporate customers' checklists every year and repeatedly submit account, permission, and log evidence
  • Mid-sized manufacturers in the middle of a smart factory transition: Companies that now need boundary management between the office network and the plant network as they connect equipment to the network
  • Companies whose core assets are drawings, recipes, and process conditions: Companies in fields such as molds, chemicals, and precision machining, where leakage of technical materials translates directly into loss of competitiveness
  • Companies preparing for ISMS-P or ISO/IEC 27001 certification: Companies that must prepare for and maintain certification with 1 to 2 dual-role administrators and no dedicated organization
  • Companies operating multiple sites or legal entities: Companies where the security level differs by plant and headquarters needs a way to see the overall status

10

Technical foundation

ItemDetails
Data model39 security-domain data tables (access control, authentication, audit, data protection, network, OT, SIEM, EDR, DLP, threat intelligence, privileged accounts, vulnerabilities, patches, training, compliance)
Screen composition45 list, detail, and dashboard screens, 22 status widgets, 13 menus
Workflows7 predefined -- security incident response, access rights management, compliance audit, SIEM threat detection (15 stages), EDR detection and response (13 stages), DLP violation handling (11 stages), patch deployment (10 stages)
Audit logsAppend-only structure, recording target, action, severity, source IP, and timestamp, 1:1 linkage with data access logs, monthly partitioned storage
Retention policyRetention period set by log type (default 90 days; 1 year, 3 years, 5 years, or permanent as requirements dictate)
Authentication3 multi-factor methods (authenticator app TOTP, SMS, email), concurrent session limits and inactivity timeouts, single sign-on (SSO) integration
EncryptionAES-256, RSA-2048, RSA-4096, ECDSA-P256 / key values held in a key management system, only metadata and rotation history tracked
Access control5 policy types (access control, authentication, data protection, network, input validation), mixed role-based and attribute-based rules, priority evaluation
OT security8 asset types (PLC, SCADA, HMI, DCS, RTU, sensors, network equipment, historians), 5 network zones (field, control, supervisory, manufacturing operations, DMZ), equipment master linkage
Multi-tenantTenant identifier-based isolation, independent operation by legal entity and site
Deployment6-stage automated deployment (data definition → API → screens → menus → routes → artifacts)

Try it yourself

Apply the ISMS (Information Security Management) template on the canvas, and data models to screens are auto-generated.

ISMS (Information Security Management) | VEXPLOR