<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>联盟数据共享 on 办公AI智能小助手</title>
    <link>https://blog.qife122.com/tags/%E8%81%94%E7%9B%9F%E6%95%B0%E6%8D%AE%E5%85%B1%E4%BA%AB/</link>
    <description>Recent content in 联盟数据共享 on 办公AI智能小助手</description>
    <generator>Hugo</generator>
    <language>zh-cn</language>
    <copyright>qife</copyright>
    <lastBuildDate>Sun, 16 Nov 2025 19:48:51 +0800</lastBuildDate>
    <atom:link href="https://blog.qife122.com/tags/%E8%81%94%E7%9B%9F%E6%95%B0%E6%8D%AE%E5%85%B1%E4%BA%AB/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ACP 240标准验证：数据安全技术赋能联盟数据共享新纪元</title>
      <link>https://blog.qife122.com/p/acp-240%E6%A0%87%E5%87%86%E9%AA%8C%E8%AF%81%E6%95%B0%E6%8D%AE%E5%AE%89%E5%85%A8%E6%8A%80%E6%9C%AF%E8%B5%8B%E8%83%BD%E8%81%94%E7%9B%9F%E6%95%B0%E6%8D%AE%E5%85%B1%E4%BA%AB%E6%96%B0%E7%BA%AA%E5%85%83/</link>
      <pubDate>Sun, 16 Nov 2025 19:48:51 +0800</pubDate>
      <guid>https://blog.qife122.com/p/acp-240%E6%A0%87%E5%87%86%E9%AA%8C%E8%AF%81%E6%95%B0%E6%8D%AE%E5%AE%89%E5%85%A8%E6%8A%80%E6%9C%AF%E8%B5%8B%E8%83%BD%E8%81%94%E7%9B%9F%E6%95%B0%E6%8D%AE%E5%85%B1%E4%BA%AB%E6%96%B0%E7%BA%AA%E5%85%83/</guid>
      <description>&lt;h1 id=&#34;operation-highmast-validates-acp-240-the-new-standard-powering-coalition-data-sharing&#34;&gt;Operation HIGHMAST Validates ACP 240: The New Standard Powering Coalition Data Sharing&lt;/h1&gt;&#xA;&lt;h2 id=&#34;the-highmast-challenge-when-networks-cant-keep-up-with-missions&#34;&gt;The HIGHMAST Challenge: When Networks Can&amp;rsquo;t Keep Up with Missions&lt;/h2&gt;&#xA;&lt;p&gt;&amp;ldquo;In the DOD, policy for a long time has been very network centric,&amp;rdquo; explains Tim Clayton, a former AWS senior solutions architect who led Mission Partner Environment efforts before joining Virtru. &amp;ldquo;If you think about networks like NIPR, SIPR, JWICS, these are classification based&amp;hellip;anytime you need to cross data between them, you have to use some sort of cross-domain solution.&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
