| Mithril (mithril.fund) |
— |
| kotoba-cloud-control-plane |
- site:bindsTo → kotoba-identity-authority (IDENTITY_AUTHORITY)
- site:bindsTo → kotoba-research-authority (RESEARCH_AUTHORITY)
- site:bindsTo → kotoba-research-authority (ORG_AUTHORITY)
- site:bindsTo → kotoba-research-authority (FAKE_REPORT_AUTHORITY)
- site:bindsTo → kotoba-cloud-database (DATABASE_SERVICE)
- site:bindsTo → kotobase-authn (AUTHN_SERVICE)
- site:serves → kotoba.cloud
- site:serves → www.kotoba.cloud
- site:serves → api.kotoba.cloud
- site:serves → console.kotoba.cloud
- site:serves → boot.kotoba.cloud
- site:serves → docs.kotoba.cloud
- site:serves → kyber.kotoba.cloud
- site:serves → knowledge.kotoba.cloud
- site:serves → data.kotoba.cloud
- site:serves → yabai.kotoba.cloud
- site:serves → blog.kotoba.cloud
- site:serves → graph.kotoba.cloud
- site:serves → support.kotoba.cloud
- site:serves → apps.kotoba.cloud
- ほか 5 件（すべては JSON-LD に）
|
| kotoba-identity-authority |
- site:serves → auth.kotoba.cloud
|
| kotoba-research-authority |
— |
| kotoba-cloud-database |
— |
| kotobase-authn |
— |
| R2 kotobase-graph-database-production (PUBLIC_BLOCKS) |
— |
| R2 internal-security-nvd (NVD_BLOCKS, read-only allow-listed keys) |
— |
| Durable Object PqKeyRegistry (SQLite, post-quantum key registry) |
— |
| Durable Object BillingAccount (SQLite) |
— |
| EDR / XDR |
- site:answers → DE.CM-01 — Networks and network services are monitored to find potentially adverse events
- site:answers → DE.CM-03 — Personnel activity and technology usage are monitored to find potentially adverse events
- site:answers → DE.CM-09 — Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
- site:answers → DE.AE-02 — Potentially adverse events are analyzed to better understand associated activities
- site:answers → DE.AE-03 — Information is correlated from multiple sources
- site:answers → DE.AE-06 — Information on adverse events is provided to authorized staff and tools
- site:answers → DE.AE-08 — Incidents are declared when adverse events meet the defined incident criteria
- site:answers → PR.PS-05 — Installation and execution of unauthorized software are prevented
- site:answers → RS.AN-03 — Analysis is performed to establish what has taken place during an incident and the root cause of the incident
- site:answers → RS.MI-01 — Incidents are contained
- site:answers → RS.MI-02 — Incidents are eradicated
|
| CMDB / 資産台帳 |
- site:answers → ID.AM-01 — Inventories of hardware managed by the organization are maintained
- site:answers → ID.AM-02 — Inventories of software, services, and systems managed by the organization are maintained
- site:answers → ID.AM-03 — Representations of the organization’s authorized network communication and internal and external network data flows are maintained
- site:answers → ID.AM-04 — Inventories of services provided by suppliers are maintained
- site:answers → ID.AM-05 — Assets are prioritized based on classification, criticality, resources, and impact on the mission
- site:answers → ID.AM-07 — Inventories of data and corresponding metadata for designated data types are maintained
- site:answers → ID.AM-08 — Systems, hardware, software, services, and data are managed throughout their life cycles
- site:answers → GV.OC-04 — Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated
- site:answers → GV.OC-05 — Outcomes, capabilities, and services that the organization depends on are understood and communicated
|
| Email Security（フィッシング対策・報告） |
- site:answers → PR.DS-02 — The confidentiality, integrity, and availability of data-in-transit are protected
- site:answers → DE.CM-01 — Networks and network services are monitored to find potentially adverse events
- site:answers → DE.AE-02 — Potentially adverse events are analyzed to better understand associated activities
- site:answers → DE.AE-06 — Information on adverse events is provided to authorized staff and tools
- site:answers → DE.AE-08 — Incidents are declared when adverse events meet the defined incident criteria
- site:answers → RS.MA-02 — Incident reports are triaged and validated
- site:answers → RS.MA-03 — Incidents are categorized and prioritized
- site:answers → RS.CO-02 — Internal and external stakeholders are notified of incidents
- site:answers → RS.CO-03 — Information is shared with designated internal and external stakeholders
- site:answers → ID.RA-02 — Cyber threat intelligence is received from information sharing forums and sources
- site:answers → ID.RA-03 — Internal and external threats to the organization are identified and recorded
- site:answers → PR.AT-01 — Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind
|
| 脆弱性管理（CTEM / DAST / SAST / VM） |
- site:answers → ID.RA-01 — Vulnerabilities in assets are identified, validated, and recorded
- site:answers → ID.RA-02 — Cyber threat intelligence is received from information sharing forums and sources
- site:answers → ID.RA-05 — Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
- site:answers → ID.RA-06 — Risk responses are chosen, prioritized, planned, tracked, and communicated
- site:answers → ID.RA-08 — Processes for receiving, analyzing, and responding to vulnerability disclosures are established
- site:answers → ID.AM-02 — Inventories of software, services, and systems managed by the organization are maintained
- site:answers → ID.AM-08 — Systems, hardware, software, services, and data are managed throughout their life cycles
- site:answers → PR.PS-02 — Software is maintained, replaced, and removed commensurate with risk
- site:answers → PR.PS-06 — Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
- site:answers → DE.CM-09 — Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
|
| CSPM / CNAPP |
- site:answers → GV.SC-07 — The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship
- site:answers → ID.AM-02 — Inventories of software, services, and systems managed by the organization are maintained
- site:answers → ID.RA-01 — Vulnerabilities in assets are identified, validated, and recorded
- site:answers → ID.RA-05 — Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
- site:answers → PR.AA-05 — Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
- site:answers → PR.PS-01 — Configuration management practices are established and applied
- site:answers → PR.IR-01 — Networks and environments are protected from unauthorized logical access and usage
- site:answers → PR.DS-01 — The confidentiality, integrity, and availability of data-at-rest are protected
- site:answers → PR.DS-11 — Backups of data are created, protected, maintained, and tested
|
| ZTNA / Private Access |
- site:answers → PR.AA-01 — Identities and credentials for authorized users, services, and hardware are managed by the organization
- site:answers → PR.AA-03 — Users, services, and hardware are authenticated
- site:answers → PR.AA-05 — Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
- site:answers → PR.IR-01 — Networks and environments are protected from unauthorized logical access and usage
|
| UEM / MDM |
- site:answers → ID.AM-01 — Inventories of hardware managed by the organization are maintained
- site:answers → ID.AM-02 — Inventories of software, services, and systems managed by the organization are maintained
- site:answers → PR.PS-01 — Configuration management practices are established and applied
- site:answers → PR.PS-02 — Software is maintained, replaced, and removed commensurate with risk
- site:answers → PR.PS-05 — Installation and execution of unauthorized software are prevented
- site:answers → PR.DS-01 — The confidentiality, integrity, and availability of data-at-rest are protected
- site:answers → PR.AA-03 — Users, services, and hardware are authenticated
|
| SIEM / SOAR |
- site:answers → PR.PS-04 — Log records are generated and made available for continuous monitoring
- site:answers → DE.CM-01 — Networks and network services are monitored to find potentially adverse events
- site:answers → DE.CM-03 — Personnel activity and technology usage are monitored to find potentially adverse events
- site:answers → DE.CM-06 — External service provider activities and services are monitored to find potentially adverse events
- site:answers → DE.CM-09 — Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
- site:answers → DE.AE-02 — Potentially adverse events are analyzed to better understand associated activities
- site:answers → DE.AE-03 — Information is correlated from multiple sources
- site:answers → DE.AE-04 — The estimated impact and scope of adverse events are understood
- site:answers → DE.AE-06 — Information on adverse events is provided to authorized staff and tools
- site:answers → DE.AE-07 — Cyber threat intelligence and other contextual information are integrated into the analysis
- site:answers → DE.AE-08 — Incidents are declared when adverse events meet the defined incident criteria
- site:answers → RS.MA-01 — The incident response plan is executed in coordination with relevant third parties once an incident is declared
- site:answers → RS.MA-02 — Incident reports are triaged and validated
- site:answers → RS.MA-03 — Incidents are categorized and prioritized
- site:answers → RS.MA-04 — Incidents are escalated or elevated as needed
- site:answers → RS.MA-05 — The criteria for initiating incident recovery are applied
- site:answers → RS.AN-03 — Analysis is performed to establish what has taken place during an incident and the root cause of the incident
- site:answers → RS.AN-06 — Actions performed during an investigation are recorded, and the records’ integrity and provenance are preserved
- site:answers → RS.AN-07 — Incident data and metadata are collected, and their integrity and provenance are preserved
- site:answers → RS.AN-08 — An incident’s magnitude is estimated and validated
- ほか 4 件（すべては JSON-LD に）
|
| GRC / 監査 |
- site:answers → GV.OC-03 — Legal, regulatory, and contractual requirements regarding cybersecurity — including privacy and civil liberties obligations — are understood and managed
- site:answers → GV.RM-02 — Risk appetite and risk tolerance statements are established, communicated, and maintained
- site:answers → GV.RM-06 — A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated
- site:answers → GV.RR-02 — Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
- site:answers → GV.PO-01 — Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
- site:answers → GV.PO-02 — Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
- site:answers → GV.OV-01 — Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction
- site:answers → GV.OV-02 — The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks
- site:answers → GV.OV-03 — Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed
- site:answers → GV.SC-04 — Suppliers are known and prioritized by criticality
- site:answers → GV.SC-05 — Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
- site:answers → GV.SC-06 — Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships
- site:answers → GV.SC-07 — The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship
- site:answers → GV.SC-08 — Relevant suppliers and other third parties are included in incident planning, response, and recovery activities
- site:answers → GV.SC-10 — Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement
- site:answers → ID.RA-05 — Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
- site:answers → ID.RA-06 — Risk responses are chosen, prioritized, planned, tracked, and communicated
- site:answers → ID.RA-07 — Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
|
| Backup / DR |
- site:answers → PR.DS-11 — Backups of data are created, protected, maintained, and tested
- site:answers → PR.IR-03 — Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
- site:answers → ID.IM-04 — Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
- site:answers → RC.RP-01 — The recovery portion of the incident response plan is executed once initiated from the incident response process
- site:answers → RC.RP-02 — Recovery actions are selected, scoped, prioritized, and performed
- site:answers → RC.RP-03 — The integrity of backups and other restoration assets is verified before using them for restoration
- site:answers → RC.RP-04 — Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms
- site:answers → RC.RP-05 — The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed
- site:answers → RC.RP-06 — The end of incident recovery is declared based on criteria, and incident- related documentation is completed
- site:answers → RC.CO-03 — Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
- site:answers → RC.CO-04 — Public updates on incident recovery are shared using approved methods and messaging
|
| kotoba-cloud-support |
— |
| kotoba-security-watch |
— |