ネクフル Product Lineup

We would like to introduce a case where our "necfru MAM/DAM" was implemented at Company M, which is engaged in CAD/CAM contract work. At this company, there was a mix of drawings/NC data versions, leading to processing errors. The data from completed projects was increasing, putting pressure on the server. Therefore, tags were standardized using project ID/model/material/version number, allowing the site to have view-only access while restricting modifications to administrators. This reduced the risk of processing errors and decreased quality loss, while also shortening data retrieval time and improving setup. [Case Overview (Partial)] ■ Challenges - Sharing with partner factories was primarily managed via USB, which was inefficient. - It took a long time for the site to find the necessary data. ■ Solutions - Final versions were stored in an official repository to prevent misuse. - Completed projects were moved to COLD storage and retrieved only when necessary. *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case study of a company engaged in CAD/CAM outsourcing that implemented the exit strategy security solution "DDHBOX." Handling customer design data makes information leakage critical, and submitting a checklist from mid-sized manufacturers has become mandatory. While there was a desire to invest in security, the lack of personnel available for operations was also a challenge. Our product was installed at the network exit to automatically block C2 communications. Upon receiving a notification, we defined the procedure of "isolation of the terminal → investigation support if necessary," and established a system to utilize monthly reports for customer explanations and internal management. 【Case Overview】 ■ Challenge: Desire to invest in security but lack of personnel for operations ■ Solution: Utilize monthly reports for customer explanations and internal management ■ Effects: - The basis for checklist responses was organized, leading to continued outsourcing - The operations became lighter, allowing for continued measures even with shared duties - The initial response and support system in case of an incident became clear *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case where Company J, a manufacturer of resin parts, implemented our "necfru MAM/DAM." The company faced challenges such as the time required to collect related documents when defects occurred. To address this, they standardized tags using part numbers, molds, lots, and revision dates. They organized related documents into sets for bulk reference and sharing. As a result, the initial response to complaints (document submission) was expedited, leading to an improvement in trust. [Case Overview (Partial)] ■Challenges - Difficulty in tracking the history of part number revisions, hindering recurrence prevention - Evidence submitted to clients was dependent on the responsible person ■Solutions - Only necessary documents were presented to clients through URL sharing - Past cases were managed as COLD, while current cases were handled as HOT *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case where the security solution "DDHBOX" for exit measures was implemented by a resin molding manufacturer. In a situation where many factory PCs were outdated and management was lagging, a client pointed out concerns about "pivoting attacks," necessitating countermeasures. Additionally, the inability to conduct daily monitoring due to outsourced IT management was also a challenge. Our product was implemented at the factory network exit to block C2 communications. Notifications were forwarded to the outsourced IT management, clarifying initial response coordination. Monthly reports are used to understand the blocking status and organize areas for improvement. [Case Overview] ■ Challenge: Inability to conduct daily monitoring due to outsourced IT management ■ Solution: Forward notifications to the outsourced IT management to clarify initial response coordination ■ Effects: - Provided countermeasures against pivoting risks, reducing client anxiety - Daily operations were streamlined to "notification confirmation + isolation when necessary" *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case study where the precision parts manufacturer implemented the exit strategy security "DDHBOX." During a security check by a business partner, they were required to have "external communication blocking," "logs," and "reporting systems," and they faced the challenge of being uneasy about data exfiltration after an intrusion, as the entry point (UTM) alone was insufficient. By adding our product inside the UTM (at the exit) to block C2 communication, they have established an operational system that can continue even with dual roles by repurposing monthly reports for internal and partner presentations. [Case Overview] ■ Challenge: No dedicated IT personnel, lacking resources for monitoring/analysis ■ Solution: Automatic notification to the administrator's email upon detection ■ Effects: - Able to provide concrete answers to key items on the checklist (monitoring/communication control/logs/reporting/emergency response/insurance) - Operations centered around notification confirmation and monthly checks, allowing for continuity even with dual roles *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case where a company engaged in testing and analysis services implemented our exit strategy security solution, "DDHBOX." The client experienced an increase in requests for confirmation regarding "information leakage measures" and "log management," and there were many data media brought in from external sources, making it impossible to eliminate infection risks completely. Additionally, there was a concern about a lack of confidence in investigations and explanations in the event of an accident. By installing our product at the exit and blocking C2 communication, we reduced the risk of data being taken out. We created procedures for device isolation and determining the need for investigation, starting from notification emails, and clarified the insurance-backed investigation/recovery/consulting support as a "last resort." 【Case Overview】 ■ Challenge: Lack of confidence in investigations/explanations in the event of an accident ■ Solution: Clarified insurance-backed investigation/recovery/consulting support as a "last resort" ■ Effects: - Prepared explanatory materials (reports, systems) for clients, making audit responses easier - Clarified initial actions during an incident, reducing the psychological burden on responsible personnel - Evaluated as "preparation including emergency response" *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case study of a company engaged in metal processing outsourcing that implemented the exit security measure "DDHBOX." They were requested by a major manufacturer to submit a security checklist and were pointed out the concern of being "used as a stepping stone" as a subcontractor/supplier. There was no dedicated information systems department, and the situation was being handled by someone with multiple responsibilities. With the introduction of our product, external unauthorized communication (C2) after an intrusion was blocked at the exit. When detected, the source IP was identified through email notifications, and procedures for isolating the terminal were established. A monthly report was created to explain the status of countermeasures both internally and externally. [Case Overview] ■ Challenge: No dedicated information systems department, handled by someone with multiple responsibilities ■ Solution: Created a format to explain the status of countermeasures both internally and externally through monthly reports ■ Effects: - The responses to the checklist became more specific, meeting the conditions for continuing the business relationship - The operational burden was low, allowing for continuity even with multiple responsibilities *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case where the electronic component manufacturer implemented our exit security solution, "DDHBOX." There was a large amount of development data (drawings/specifications), and the responsibility for the risk of data leakage was significant. The situation was further complicated by the introduction of partner company terminals and the use of VPNs, which increased potential entry points. By installing our product at the exit (inside the FW/UTM), C2 communications are automatically blocked. The source IP is identified through notification emails, allowing for the rapid isolation of the affected terminal. Monthly reports are utilized as documentation for client audits. [Case Overview] ■ Challenge: Lack of budget/personnel to contract a SOC ■ Solution: Share monthly reports with management and use them as documentation for client audits ■ Effects: - An additional layer has been added to stop "external communications after intrusion," increasing peace of mind. - Even when detection occurs, the combination of blocking and notifications has improved initial response times. *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case where Company A, a manufacturer of automotive parts, implemented our "necfru MAM/DAM." The company was facing increasing volumes of past project drawings, leading to capacity constraints. To address this, they loaded the finalized versions into the MAM system and clarified version management. After implementation, the search for drawings transitioned from being "dependent on the person in charge" to being self-resolved in a matter of minutes. This helped reduce the storage costs for past projects. [Case Overview (Partial)] ■ Challenges - Proliferation of NAS/file servers at each location - Concerns about sharing drawings with suppliers via email/USB ■ Solutions - Cross-search using part numbers, processes, and equipment tags - External sharing through URLs with permissions to publish only the necessary scope *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case where our "necfru MAM/DAM" was implemented at an aircraft parts manufacturer. The company faced challenges due to a large volume of data per project, leading to storage constraints. Additionally, there were demands for the presentation of versions/audit trails during audits. To address this, they organized tags by project/part number/process/type of inspection, stored the finalized versions in an official repository, and fixed the versions. As a result, the submission of materials during audits became faster, and the mixing of versions decreased, which helped reduce reference errors. [Case Overview (Partial)] ■ Challenges - Sharing with partner companies raises concerns about information leakage. - Business stoppage during on-premises failures poses a significant risk. ■ Solution - External sharing is limited in scope and can be tracked via logs. - Initially, small-scale verification was conducted with representative projects, gradually expanding from there. *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case where our "necfru MAM/DAM" was implemented at Company G, which engages in testing and analysis outsourcing services. At this company, testing data was dispersed across different projects, making it difficult to re-search. Therefore, we standardized tags by project ID, testing conditions, equipment, and date. We proposed a method for managing deliverables as sets and sharing them in a limited manner via URL. Customer responses (resending/additional requests) became faster, and the delivery procedures were standardized, resulting in a reduction of errors. 【Case Overview (Partial)】 ■ Issues - The means of delivering large volumes of data to customers were inconsistent. - It was impossible to track replacement history after delivery. ■ Solutions - The final version is compiled, and replacements are managed as versions. - Completed projects are moved to COLD to optimize storage costs. *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case study of the implementation of our "necfru drive" at Company G, which conducts testing and analysis outsourcing services. The company faced the challenge of having testing data dispersed by project, making it time-consuming to re-search for necessary information. To address this, they standardized tags based on axes such as project ID, testing conditions, equipment used, and date, and organized the data. Additionally, they managed deliverables on a set basis and established a system for limited sharing via URL. As a result, the speed of response to customer resends and additional requests improved, and the standardization of the delivery flow led to a reduction in errors. 【Case Overview (Partial)】 ■Challenges - The means of delivering large-volume data were not standardized. - It was difficult to track replacement history after delivery. ■Response Actions - Stored based on the finalized version, with replacements managed through version control. - Completed projects were moved to a COLD area to reduce storage costs. ＼Free helpful materials available／ *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case study of our "necfru drive" implementation at an aircraft parts manufacturer. The company faced challenges due to large data volumes for each project, which were putting pressure on storage areas, as well as the requirement to present versions and audit trails during audits. To address this, they organized tags by project, part number, process, and inspection type, consolidating the finalized versions into an official repository to fix the versions. As a result, the submission of documents for audit responses became smoother, and the mixing of versions decreased, leading to a reduction in reference errors. [Case Overview (Partial)] ■ Challenges - Concerns about the risk of information leakage when sharing with partner companies - High risk of business interruption during on-premises failures ■ Response Measures - Limited the scope of external sharing and made it traceable through logs - Started small with representative projects and gradually expanded ＼Helpful materials are available／ *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case study of the implementation of our "necfru drive" at Company M, which provides CAD/CAM contract services. The company faced challenges such as the mixing of drawings and NC data leading to processing errors, as well as server capacity being strained due to the increase in completed project data. To address this, they standardized tags by project ID, model, material, and version number, and switched to an operation where the site could only view data, with updates limited to administrators. As a result, the risk of processing errors was reduced, leading to a decrease in quality loss. Additionally, the time required for data searches was shortened, contributing to improved efficiency in setup. 【Case Overview (Partial)】 ■Challenges - Data sharing with partner factories was primarily managed via USB, making it difficult to manage. - It took time to find the necessary data on-site. ■Response - Consolidated finalized versions in an official repository to prevent misuse. - Moved completed projects to a COLD area, retrieving them only when necessary. ＼Free helpful materials available／ *For more details, please download the PDF or feel free to contact us.

We would like to introduce a case study of our "necfru drive" implementation at J Company, a resin parts manufacturer. The company faced challenges with the time it took to collect related documents when issues occurred. To address this, they standardized tags by part number, mold, lot, and revision date, allowing related documents to be bundled for easy reference and sharing. As a result, the initial response time during complaint handling (document submission) has been expedited, leading to increased trust from clients. 【Case Overview (Partial)】 ■Challenges - Difficulties in tracking the history of part number revisions, hindering recurrence prevention. - Dependence on specific personnel for submitting evidence to clients. ■Response Measures - Only necessary documents are provided to clients through URL sharing. - Past projects are managed as COLD, while current projects are handled as HOT for organization. ＼Free Helpful Materials Available／ *For more details, please download the PDF or feel free to contact us.