@aws-sdk/client-securityhub 3.714.0 → 3.719.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist-types/models/models_0.d.ts +45 -982
- package/dist-types/models/models_1.d.ts +50 -938
- package/dist-types/models/models_2.d.ts +36 -481
- package/package.json +12 -12
|
@@ -1334,31 +1334,7 @@ export interface ContainerDetails {
|
|
|
1334
1334
|
ImageName?: string | undefined;
|
|
1335
1335
|
/**
|
|
1336
1336
|
* <p>Indicates when the container started.</p>
|
|
1337
|
-
* <p>
|
|
1338
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
1339
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
1340
|
-
* <ul>
|
|
1341
|
-
* <li>
|
|
1342
|
-
* <p>
|
|
1343
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
1344
|
-
* </li>
|
|
1345
|
-
* <li>
|
|
1346
|
-
* <p>
|
|
1347
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
1348
|
-
* </li>
|
|
1349
|
-
* <li>
|
|
1350
|
-
* <p>
|
|
1351
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
1352
|
-
* </li>
|
|
1353
|
-
* <li>
|
|
1354
|
-
* <p>
|
|
1355
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
1356
|
-
* </li>
|
|
1357
|
-
* <li>
|
|
1358
|
-
* <p>
|
|
1359
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
1360
|
-
* </li>
|
|
1361
|
-
* </ul>
|
|
1337
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
1362
1338
|
* @public
|
|
1363
1339
|
*/
|
|
1364
1340
|
LaunchedAt?: string | undefined;
|
|
@@ -1818,7 +1794,7 @@ export interface ResourceDetails {
|
|
|
1818
1794
|
AwsEc2LaunchTemplate?: AwsEc2LaunchTemplateDetails | undefined;
|
|
1819
1795
|
/**
|
|
1820
1796
|
* <p>
|
|
1821
|
-
* Provides details about an Amazon SageMaker notebook instance.
|
|
1797
|
+
* Provides details about an Amazon SageMaker AI notebook instance.
|
|
1822
1798
|
* </p>
|
|
1823
1799
|
* @public
|
|
1824
1800
|
*/
|
|
@@ -2208,31 +2184,7 @@ export interface ThreatIntelIndicator {
|
|
|
2208
2184
|
/**
|
|
2209
2185
|
* <p>Indicates when the most recent instance of a threat intelligence indicator was
|
|
2210
2186
|
* observed.</p>
|
|
2211
|
-
* <p>
|
|
2212
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2213
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2214
|
-
* <ul>
|
|
2215
|
-
* <li>
|
|
2216
|
-
* <p>
|
|
2217
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2218
|
-
* </li>
|
|
2219
|
-
* <li>
|
|
2220
|
-
* <p>
|
|
2221
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2222
|
-
* </li>
|
|
2223
|
-
* <li>
|
|
2224
|
-
* <p>
|
|
2225
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2226
|
-
* </li>
|
|
2227
|
-
* <li>
|
|
2228
|
-
* <p>
|
|
2229
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2230
|
-
* </li>
|
|
2231
|
-
* <li>
|
|
2232
|
-
* <p>
|
|
2233
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2234
|
-
* </li>
|
|
2235
|
-
* </ul>
|
|
2187
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
2236
2188
|
* @public
|
|
2237
2189
|
*/
|
|
2238
2190
|
LastObservedAt?: string | undefined;
|
|
@@ -2461,61 +2413,13 @@ export interface VulnerabilityVendor {
|
|
|
2461
2413
|
VendorSeverity?: string | undefined;
|
|
2462
2414
|
/**
|
|
2463
2415
|
* <p>Indicates when the vulnerability advisory was created.</p>
|
|
2464
|
-
* <p>
|
|
2465
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2466
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2467
|
-
* <ul>
|
|
2468
|
-
* <li>
|
|
2469
|
-
* <p>
|
|
2470
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2471
|
-
* </li>
|
|
2472
|
-
* <li>
|
|
2473
|
-
* <p>
|
|
2474
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2475
|
-
* </li>
|
|
2476
|
-
* <li>
|
|
2477
|
-
* <p>
|
|
2478
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2479
|
-
* </li>
|
|
2480
|
-
* <li>
|
|
2481
|
-
* <p>
|
|
2482
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2483
|
-
* </li>
|
|
2484
|
-
* <li>
|
|
2485
|
-
* <p>
|
|
2486
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2487
|
-
* </li>
|
|
2488
|
-
* </ul>
|
|
2416
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
2489
2417
|
* @public
|
|
2490
2418
|
*/
|
|
2491
2419
|
VendorCreatedAt?: string | undefined;
|
|
2492
2420
|
/**
|
|
2493
2421
|
* <p>Indicates when the vulnerability advisory was last updated.</p>
|
|
2494
|
-
* <p>
|
|
2495
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2496
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2497
|
-
* <ul>
|
|
2498
|
-
* <li>
|
|
2499
|
-
* <p>
|
|
2500
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2501
|
-
* </li>
|
|
2502
|
-
* <li>
|
|
2503
|
-
* <p>
|
|
2504
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2505
|
-
* </li>
|
|
2506
|
-
* <li>
|
|
2507
|
-
* <p>
|
|
2508
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2509
|
-
* </li>
|
|
2510
|
-
* <li>
|
|
2511
|
-
* <p>
|
|
2512
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2513
|
-
* </li>
|
|
2514
|
-
* <li>
|
|
2515
|
-
* <p>
|
|
2516
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2517
|
-
* </li>
|
|
2518
|
-
* </ul>
|
|
2422
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
2519
2423
|
* @public
|
|
2520
2424
|
*/
|
|
2521
2425
|
VendorUpdatedAt?: string | undefined;
|
|
@@ -2815,123 +2719,26 @@ export interface AwsSecurityFinding {
|
|
|
2815
2719
|
/**
|
|
2816
2720
|
* <p>Indicates when the security findings provider first observed the potential security
|
|
2817
2721
|
* issue that a finding captured.</p>
|
|
2818
|
-
* <p>
|
|
2819
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2820
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2821
|
-
* <ul>
|
|
2822
|
-
* <li>
|
|
2823
|
-
* <p>
|
|
2824
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2825
|
-
* </li>
|
|
2826
|
-
* <li>
|
|
2827
|
-
* <p>
|
|
2828
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2829
|
-
* </li>
|
|
2830
|
-
* <li>
|
|
2831
|
-
* <p>
|
|
2832
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2833
|
-
* </li>
|
|
2834
|
-
* <li>
|
|
2835
|
-
* <p>
|
|
2836
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2837
|
-
* </li>
|
|
2838
|
-
* <li>
|
|
2839
|
-
* <p>
|
|
2840
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2841
|
-
* </li>
|
|
2842
|
-
* </ul>
|
|
2722
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
2843
2723
|
* @public
|
|
2844
2724
|
*/
|
|
2845
2725
|
FirstObservedAt?: string | undefined;
|
|
2846
2726
|
/**
|
|
2847
|
-
* <p>Indicates when the security findings provider most recently observed the
|
|
2848
|
-
*
|
|
2849
|
-
* <p>This field accepts only the specified formats. Timestamps
|
|
2850
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2851
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2852
|
-
* <ul>
|
|
2853
|
-
* <li>
|
|
2854
|
-
* <p>
|
|
2855
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2856
|
-
* </li>
|
|
2857
|
-
* <li>
|
|
2858
|
-
* <p>
|
|
2859
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2860
|
-
* </li>
|
|
2861
|
-
* <li>
|
|
2862
|
-
* <p>
|
|
2863
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2864
|
-
* </li>
|
|
2865
|
-
* <li>
|
|
2866
|
-
* <p>
|
|
2867
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2868
|
-
* </li>
|
|
2869
|
-
* <li>
|
|
2870
|
-
* <p>
|
|
2871
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2872
|
-
* </li>
|
|
2873
|
-
* </ul>
|
|
2727
|
+
* <p>Indicates when the security findings provider most recently observed a change in the resource that is involved in the finding.</p>
|
|
2728
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
2874
2729
|
* @public
|
|
2875
2730
|
*/
|
|
2876
2731
|
LastObservedAt?: string | undefined;
|
|
2877
2732
|
/**
|
|
2878
2733
|
* <p>Indicates when the security findings provider created the potential security issue that
|
|
2879
2734
|
* a finding captured.</p>
|
|
2880
|
-
* <p>
|
|
2881
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2882
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2883
|
-
* <ul>
|
|
2884
|
-
* <li>
|
|
2885
|
-
* <p>
|
|
2886
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2887
|
-
* </li>
|
|
2888
|
-
* <li>
|
|
2889
|
-
* <p>
|
|
2890
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2891
|
-
* </li>
|
|
2892
|
-
* <li>
|
|
2893
|
-
* <p>
|
|
2894
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2895
|
-
* </li>
|
|
2896
|
-
* <li>
|
|
2897
|
-
* <p>
|
|
2898
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2899
|
-
* </li>
|
|
2900
|
-
* <li>
|
|
2901
|
-
* <p>
|
|
2902
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2903
|
-
* </li>
|
|
2904
|
-
* </ul>
|
|
2735
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
2905
2736
|
* @public
|
|
2906
2737
|
*/
|
|
2907
2738
|
CreatedAt: string | undefined;
|
|
2908
2739
|
/**
|
|
2909
2740
|
* <p>Indicates when the security findings provider last updated the finding record.</p>
|
|
2910
|
-
* <p>
|
|
2911
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
2912
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
2913
|
-
* <ul>
|
|
2914
|
-
* <li>
|
|
2915
|
-
* <p>
|
|
2916
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
2917
|
-
* </li>
|
|
2918
|
-
* <li>
|
|
2919
|
-
* <p>
|
|
2920
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
2921
|
-
* </li>
|
|
2922
|
-
* <li>
|
|
2923
|
-
* <p>
|
|
2924
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
2925
|
-
* </li>
|
|
2926
|
-
* <li>
|
|
2927
|
-
* <p>
|
|
2928
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
2929
|
-
* </li>
|
|
2930
|
-
* <li>
|
|
2931
|
-
* <p>
|
|
2932
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
2933
|
-
* </li>
|
|
2934
|
-
* </ul>
|
|
2741
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
2935
2742
|
* @public
|
|
2936
2743
|
*/
|
|
2937
2744
|
UpdatedAt: string | undefined;
|
|
@@ -3111,31 +2918,7 @@ export interface AwsSecurityFinding {
|
|
|
3111
2918
|
GeneratorDetails?: GeneratorDetails | undefined;
|
|
3112
2919
|
/**
|
|
3113
2920
|
* <p>A timestamp that indicates when Security Hub received a finding and begins to process it.</p>
|
|
3114
|
-
* <p>
|
|
3115
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3116
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3117
|
-
* <ul>
|
|
3118
|
-
* <li>
|
|
3119
|
-
* <p>
|
|
3120
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3121
|
-
* </li>
|
|
3122
|
-
* <li>
|
|
3123
|
-
* <p>
|
|
3124
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3125
|
-
* </li>
|
|
3126
|
-
* <li>
|
|
3127
|
-
* <p>
|
|
3128
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3129
|
-
* </li>
|
|
3130
|
-
* <li>
|
|
3131
|
-
* <p>
|
|
3132
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3133
|
-
* </li>
|
|
3134
|
-
* <li>
|
|
3135
|
-
* <p>
|
|
3136
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3137
|
-
* </li>
|
|
3138
|
-
* </ul>
|
|
2921
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
3139
2922
|
* @public
|
|
3140
2923
|
*/
|
|
3141
2924
|
ProcessedAt?: string | undefined;
|
|
@@ -3151,7 +2934,7 @@ export interface AwsSecurityFinding {
|
|
|
3151
2934
|
* <p>
|
|
3152
2935
|
* Provides details about an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack
|
|
3153
2936
|
* sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you
|
|
3154
|
-
* must have GuardDuty
|
|
2937
|
+
* must have GuardDuty enabled. For more information, see <a href="https://docs.aws.amazon.com/guardduty/latest/ug/guardduty-extended-threat-detection.html">GuardDuty Extended Threat Detection </a> in the <i>Amazon GuardDuty User Guide</i>.
|
|
3155
2938
|
* </p>
|
|
3156
2939
|
* @public
|
|
3157
2940
|
*/
|
|
@@ -3235,124 +3018,27 @@ export interface AwsSecurityFindingFilters {
|
|
|
3235
3018
|
/**
|
|
3236
3019
|
* <p>A timestamp that indicates when the security findings provider first
|
|
3237
3020
|
* observed the potential security issue that a finding captured.</p>
|
|
3238
|
-
* <p>
|
|
3239
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3240
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3241
|
-
* <ul>
|
|
3242
|
-
* <li>
|
|
3243
|
-
* <p>
|
|
3244
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3245
|
-
* </li>
|
|
3246
|
-
* <li>
|
|
3247
|
-
* <p>
|
|
3248
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3249
|
-
* </li>
|
|
3250
|
-
* <li>
|
|
3251
|
-
* <p>
|
|
3252
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3253
|
-
* </li>
|
|
3254
|
-
* <li>
|
|
3255
|
-
* <p>
|
|
3256
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3257
|
-
* </li>
|
|
3258
|
-
* <li>
|
|
3259
|
-
* <p>
|
|
3260
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3261
|
-
* </li>
|
|
3262
|
-
* </ul>
|
|
3021
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
3263
3022
|
* @public
|
|
3264
3023
|
*/
|
|
3265
3024
|
FirstObservedAt?: DateFilter[] | undefined;
|
|
3266
3025
|
/**
|
|
3267
|
-
* <p>A timestamp that indicates when the security findings provider most
|
|
3268
|
-
*
|
|
3269
|
-
* <p>This field accepts only the specified formats. Timestamps
|
|
3270
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3271
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3272
|
-
* <ul>
|
|
3273
|
-
* <li>
|
|
3274
|
-
* <p>
|
|
3275
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3276
|
-
* </li>
|
|
3277
|
-
* <li>
|
|
3278
|
-
* <p>
|
|
3279
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3280
|
-
* </li>
|
|
3281
|
-
* <li>
|
|
3282
|
-
* <p>
|
|
3283
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3284
|
-
* </li>
|
|
3285
|
-
* <li>
|
|
3286
|
-
* <p>
|
|
3287
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3288
|
-
* </li>
|
|
3289
|
-
* <li>
|
|
3290
|
-
* <p>
|
|
3291
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3292
|
-
* </li>
|
|
3293
|
-
* </ul>
|
|
3026
|
+
* <p>A timestamp that indicates when the security findings provider most recently observed a change in the resource that is involved in the finding.</p>
|
|
3027
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
3294
3028
|
* @public
|
|
3295
3029
|
*/
|
|
3296
3030
|
LastObservedAt?: DateFilter[] | undefined;
|
|
3297
3031
|
/**
|
|
3298
3032
|
* <p>A timestamp that indicates when the security findings provider
|
|
3299
3033
|
* created the potential security issue that a finding reflects.</p>
|
|
3300
|
-
* <p>
|
|
3301
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3302
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3303
|
-
* <ul>
|
|
3304
|
-
* <li>
|
|
3305
|
-
* <p>
|
|
3306
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3307
|
-
* </li>
|
|
3308
|
-
* <li>
|
|
3309
|
-
* <p>
|
|
3310
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3311
|
-
* </li>
|
|
3312
|
-
* <li>
|
|
3313
|
-
* <p>
|
|
3314
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3315
|
-
* </li>
|
|
3316
|
-
* <li>
|
|
3317
|
-
* <p>
|
|
3318
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3319
|
-
* </li>
|
|
3320
|
-
* <li>
|
|
3321
|
-
* <p>
|
|
3322
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3323
|
-
* </li>
|
|
3324
|
-
* </ul>
|
|
3034
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
3325
3035
|
* @public
|
|
3326
3036
|
*/
|
|
3327
3037
|
CreatedAt?: DateFilter[] | undefined;
|
|
3328
3038
|
/**
|
|
3329
3039
|
* <p>A timestamp that indicates when the security findings provider last
|
|
3330
3040
|
* updated the finding record.</p>
|
|
3331
|
-
* <p>
|
|
3332
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3333
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3334
|
-
* <ul>
|
|
3335
|
-
* <li>
|
|
3336
|
-
* <p>
|
|
3337
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3338
|
-
* </li>
|
|
3339
|
-
* <li>
|
|
3340
|
-
* <p>
|
|
3341
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3342
|
-
* </li>
|
|
3343
|
-
* <li>
|
|
3344
|
-
* <p>
|
|
3345
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3346
|
-
* </li>
|
|
3347
|
-
* <li>
|
|
3348
|
-
* <p>
|
|
3349
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3350
|
-
* </li>
|
|
3351
|
-
* <li>
|
|
3352
|
-
* <p>
|
|
3353
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3354
|
-
* </li>
|
|
3355
|
-
* </ul>
|
|
3041
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
3356
3042
|
* @public
|
|
3357
3043
|
*/
|
|
3358
3044
|
UpdatedAt?: DateFilter[] | undefined;
|
|
@@ -3533,61 +3219,13 @@ export interface AwsSecurityFindingFilters {
|
|
|
3533
3219
|
ProcessParentPid?: NumberFilter[] | undefined;
|
|
3534
3220
|
/**
|
|
3535
3221
|
* <p>A timestamp that identifies when the process was launched.</p>
|
|
3536
|
-
* <p>
|
|
3537
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3538
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3539
|
-
* <ul>
|
|
3540
|
-
* <li>
|
|
3541
|
-
* <p>
|
|
3542
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3543
|
-
* </li>
|
|
3544
|
-
* <li>
|
|
3545
|
-
* <p>
|
|
3546
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3547
|
-
* </li>
|
|
3548
|
-
* <li>
|
|
3549
|
-
* <p>
|
|
3550
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3551
|
-
* </li>
|
|
3552
|
-
* <li>
|
|
3553
|
-
* <p>
|
|
3554
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3555
|
-
* </li>
|
|
3556
|
-
* <li>
|
|
3557
|
-
* <p>
|
|
3558
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3559
|
-
* </li>
|
|
3560
|
-
* </ul>
|
|
3222
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
3561
3223
|
* @public
|
|
3562
3224
|
*/
|
|
3563
3225
|
ProcessLaunchedAt?: DateFilter[] | undefined;
|
|
3564
3226
|
/**
|
|
3565
3227
|
* <p>A timestamp that identifies when the process was terminated.</p>
|
|
3566
|
-
* <p>
|
|
3567
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3568
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3569
|
-
* <ul>
|
|
3570
|
-
* <li>
|
|
3571
|
-
* <p>
|
|
3572
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3573
|
-
* </li>
|
|
3574
|
-
* <li>
|
|
3575
|
-
* <p>
|
|
3576
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3577
|
-
* </li>
|
|
3578
|
-
* <li>
|
|
3579
|
-
* <p>
|
|
3580
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3581
|
-
* </li>
|
|
3582
|
-
* <li>
|
|
3583
|
-
* <p>
|
|
3584
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3585
|
-
* </li>
|
|
3586
|
-
* <li>
|
|
3587
|
-
* <p>
|
|
3588
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3589
|
-
* </li>
|
|
3590
|
-
* </ul>
|
|
3228
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
3591
3229
|
* @public
|
|
3592
3230
|
*/
|
|
3593
3231
|
ProcessTerminatedAt?: DateFilter[] | undefined;
|
|
@@ -3608,6 +3246,7 @@ export interface AwsSecurityFindingFilters {
|
|
|
3608
3246
|
ThreatIntelIndicatorCategory?: StringFilter[] | undefined;
|
|
3609
3247
|
/**
|
|
3610
3248
|
* <p>A timestamp that identifies the last observation of a threat intelligence indicator.</p>
|
|
3249
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
3611
3250
|
* @public
|
|
3612
3251
|
*/
|
|
3613
3252
|
ThreatIntelIndicatorLastObservedAt?: DateFilter[] | undefined;
|
|
@@ -3746,31 +3385,7 @@ export interface AwsSecurityFindingFilters {
|
|
|
3746
3385
|
ResourceContainerImageName?: StringFilter[] | undefined;
|
|
3747
3386
|
/**
|
|
3748
3387
|
* <p>A timestamp that identifies when the container was started.</p>
|
|
3749
|
-
* <p>
|
|
3750
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
3751
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
3752
|
-
* <ul>
|
|
3753
|
-
* <li>
|
|
3754
|
-
* <p>
|
|
3755
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
3756
|
-
* </li>
|
|
3757
|
-
* <li>
|
|
3758
|
-
* <p>
|
|
3759
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
3760
|
-
* </li>
|
|
3761
|
-
* <li>
|
|
3762
|
-
* <p>
|
|
3763
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
3764
|
-
* </li>
|
|
3765
|
-
* <li>
|
|
3766
|
-
* <p>
|
|
3767
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
3768
|
-
* </li>
|
|
3769
|
-
* <li>
|
|
3770
|
-
* <p>
|
|
3771
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
3772
|
-
* </li>
|
|
3773
|
-
* </ul>
|
|
3388
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
3774
3389
|
* @public
|
|
3775
3390
|
*/
|
|
3776
3391
|
ResourceContainerLaunchedAt?: DateFilter[] | undefined;
|
|
@@ -6700,6 +6315,12 @@ export interface DescribeHubResponse {
|
|
|
6700
6315
|
* enabled.</p>
|
|
6701
6316
|
* <p>If set to <code>true</code>, then new controls for enabled standards are enabled
|
|
6702
6317
|
* automatically. If set to <code>false</code>, then new controls are not enabled.</p>
|
|
6318
|
+
* <p>When you automatically enable new controls, you can interact with the controls in
|
|
6319
|
+
* the console and programmatically immediately after release. However, automatically enabled controls have a temporary default status of
|
|
6320
|
+
* <code>DISABLED</code>. It can take up to several days for Security Hub to process the control release and designate the
|
|
6321
|
+
* control as <code>ENABLED</code> in your account. During the processing period, you can manually enable or disable a
|
|
6322
|
+
* control, and Security Hub will maintain that designation regardless of whether you have <code>AutoEnableControls</code> set to
|
|
6323
|
+
* <code>true</code>.</p>
|
|
6703
6324
|
* @public
|
|
6704
6325
|
*/
|
|
6705
6326
|
AutoEnableControls?: boolean | undefined;
|
|
@@ -7391,31 +7012,7 @@ export interface FindingHistoryRecord {
|
|
|
7391
7012
|
/**
|
|
7392
7013
|
* <p> A timestamp that indicates when Security Hub
|
|
7393
7014
|
* processed the updated finding record.</p>
|
|
7394
|
-
* <p>
|
|
7395
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
7396
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
7397
|
-
* <ul>
|
|
7398
|
-
* <li>
|
|
7399
|
-
* <p>
|
|
7400
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
7401
|
-
* </li>
|
|
7402
|
-
* <li>
|
|
7403
|
-
* <p>
|
|
7404
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
7405
|
-
* </li>
|
|
7406
|
-
* <li>
|
|
7407
|
-
* <p>
|
|
7408
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
7409
|
-
* </li>
|
|
7410
|
-
* <li>
|
|
7411
|
-
* <p>
|
|
7412
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
7413
|
-
* </li>
|
|
7414
|
-
* <li>
|
|
7415
|
-
* <p>
|
|
7416
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
7417
|
-
* </li>
|
|
7418
|
-
* </ul>
|
|
7015
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
7419
7016
|
* @public
|
|
7420
7017
|
*/
|
|
7421
7018
|
UpdateTime?: Date | undefined;
|
|
@@ -7732,31 +7329,7 @@ export interface GetFindingHistoryRequest {
|
|
|
7732
7329
|
* returns finding history from the CreatedAt timestamp of the finding to the time at which
|
|
7733
7330
|
* the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is
|
|
7734
7331
|
* limited to 90 days.</p>
|
|
7735
|
-
* <p>
|
|
7736
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
7737
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
7738
|
-
* <ul>
|
|
7739
|
-
* <li>
|
|
7740
|
-
* <p>
|
|
7741
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
7742
|
-
* </li>
|
|
7743
|
-
* <li>
|
|
7744
|
-
* <p>
|
|
7745
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
7746
|
-
* </li>
|
|
7747
|
-
* <li>
|
|
7748
|
-
* <p>
|
|
7749
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
7750
|
-
* </li>
|
|
7751
|
-
* <li>
|
|
7752
|
-
* <p>
|
|
7753
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
7754
|
-
* </li>
|
|
7755
|
-
* <li>
|
|
7756
|
-
* <p>
|
|
7757
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
7758
|
-
* </li>
|
|
7759
|
-
* </ul>
|
|
7332
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
7760
7333
|
* @public
|
|
7761
7334
|
*/
|
|
7762
7335
|
StartTime?: Date | undefined;
|
|
@@ -7772,31 +7345,7 @@ export interface GetFindingHistoryRequest {
|
|
|
7772
7345
|
* returns finding history from the CreatedAt timestamp of the finding to the time at which
|
|
7773
7346
|
* the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is
|
|
7774
7347
|
* limited to 90 days.</p>
|
|
7775
|
-
* <p>
|
|
7776
|
-
* can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
|
|
7777
|
-
* to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
|
|
7778
|
-
* <ul>
|
|
7779
|
-
* <li>
|
|
7780
|
-
* <p>
|
|
7781
|
-
* <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
|
|
7782
|
-
* </li>
|
|
7783
|
-
* <li>
|
|
7784
|
-
* <p>
|
|
7785
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
|
|
7786
|
-
* </li>
|
|
7787
|
-
* <li>
|
|
7788
|
-
* <p>
|
|
7789
|
-
* <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
|
|
7790
|
-
* </li>
|
|
7791
|
-
* <li>
|
|
7792
|
-
* <p>
|
|
7793
|
-
* <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
|
|
7794
|
-
* </li>
|
|
7795
|
-
* <li>
|
|
7796
|
-
* <p>
|
|
7797
|
-
* <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
|
|
7798
|
-
* </li>
|
|
7799
|
-
* </ul>
|
|
7348
|
+
* <p>For more information about the validation and formatting of timestamp fields in Security Hub, see <a href="https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html#timestamps">Timestamps</a>.</p>
|
|
7800
7349
|
* @public
|
|
7801
7350
|
*/
|
|
7802
7351
|
EndTime?: Date | undefined;
|
|
@@ -9340,6 +8889,12 @@ export interface UpdateSecurityHubConfigurationRequest {
|
|
|
9340
8889
|
* <p>By default, this is set to <code>true</code>, and new controls are enabled
|
|
9341
8890
|
* automatically. To not automatically enable new controls, set this to <code>false</code>.
|
|
9342
8891
|
* </p>
|
|
8892
|
+
* <p>When you automatically enable new controls, you can interact with the controls in
|
|
8893
|
+
* the console and programmatically immediately after release. However, automatically enabled controls have a temporary default status of
|
|
8894
|
+
* <code>DISABLED</code>. It can take up to several days for Security Hub to process the control release and designate the
|
|
8895
|
+
* control as <code>ENABLED</code> in your account. During the processing period, you can manually enable or disable a
|
|
8896
|
+
* control, and Security Hub will maintain that designation regardless of whether you have <code>AutoEnableControls</code> set to
|
|
8897
|
+
* <code>true</code>.</p>
|
|
9343
8898
|
* @public
|
|
9344
8899
|
*/
|
|
9345
8900
|
AutoEnableControls?: boolean | undefined;
|