Comments (6)
I guess we need a DELETE
on this too.
from cti-taxii2.
From my perspective, I do not see why this should be part of TAXII. TAXII is not supposed to be a database API, nor should it be trying to be the one-and-only API that a security product use.
from cti-taxii2.
I think this should be optional. I don't think every server needs to implement it.
from cti-taxii2.
We know that organizations will want to, for example, share malware samples via TAXII. Doing this in STIX is really kind of ugly, and we know that. It would be nice if TAXII allowed you to deliver this. In fact, we have talked about needing this sort of feature for some time.
from cti-taxii2.
@jordan2175 I think it is very weird to assume someone wants to POST and GET raw malware samples without any STIX, via TAXII. That use case makes no sense to me at all. All of the use cases around sharing malware with TAXII include the context in a STIX document. Otherwise you've just make a really complicated API around an object store.
TAXII is not an FTP server or a web object store. Object stores already exist, we should not be trying to re-invent the wheel here.
from cti-taxii2.
The BLOBs would not be posted without STIX. They'd be tied via the url
field of STIX Artifact objects in the TAXII server.
from cti-taxii2.
Related Issues (20)
- What is the purpose of Discovery API roots having different domains in the list of api_roots ? HOT 2
- API Root Resource does not define the URL of the resource? HOT 2
- Typo in url prop of section 5.4 HOT 2
- Change integer to be 54 bits in size per RFC 7493 HOT 1
- If collections permission has false for CanRead and CanWrite, does user have permissions to see existence of Collection?
- RFE: Add additional Supported Fields to TAXII Filtering HOT 1
- Potential confusion with errors when adding duplicate objects
- Potential Confusion on Get Object Manifests
- Potentially misleading table in TAXII spec
- Typos in the TAXII spec
- Manifest & Versions Resource missing `next` Property HOT 1
- Additional URL query parameters
- Match field formatting
- "Incorrect" Spelling
- TAXII filtering is ambiguous when handling spec_version and version match fields
- Need to add the more pagination property to the manifest resource HOT 1
- Rename the spec_versions url filter parameter to be singular HOT 1
- Make the TAXII Envelope contain a list of objects not a bundle HOT 2
- Add text to explain status counts when server has yet to start processing request HOT 1
- Consider renaming the status value of pending to processing HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cti-taxii2.